Merge tag 'Ghidra_9.1_build' into patch

Author: ryanmkurtz

.github/ISSUE_TEMPLATE/bug_report.md

@@ -8,7 +8,7 @@ assignees: ''
 ---
 
 **Describe the bug**
-A clear and concise description of what the bug is.
+A clear and concise description of the bug.
 
 **To Reproduce**
 Steps to reproduce the behavior:

.github/ISSUE_TEMPLATE/question.md

@@ -1,10 +1,8 @@
 ---
 name: Question
-about: Ask a question from the developers
+about: Ask the developers a question
 title: ''
 labels: question
 assignees: ''
 
 ---
-
-

.gitignore

@@ -3,6 +3,7 @@ ghidra.repos.config
 
 # Misc files produced while executing application
 repositories/
+flatRepo/
 Ghidra/.ghidraSvrKeys
 wrapper.log*
 
@@ -62,3 +63,9 @@ Release
 .project
 .classpath
 .settings/
+
+# Ignore XTEXT generated dirs/files
+*/*/*/*/xtend-gen
+*/*/*/*/src-gen
+*/*/*/*/model/generated
+*/*/*/*/test-bin

.gitlab-ci.yml

@@ -0,0 +1,14 @@
+stages:
+  - test
+
+test-parallel:
+  stage: test
+  script:
+    - echo $REPO_TOKEN
+    - "curl -X POST -F token=$REPO_TOKEN -F ref=$CI_COMMIT_REF_NAME $REPO_URL"
+  tags:
+    - docker
+    - ghidratest 
+  image: ghidra/ubuntu
+  only:
+    - master

CONTRIBUTING.md

@@ -29,7 +29,7 @@ Patches should be submitted in the form of Pull Requests to the Ghidra
 [repository] on GitHub. But first, consider the following tips to ensure a
 smooth process when submitting a patch:
 
-- Ensure that the patch compiles and does not break any build-time tests
+- Ensure that the patch compiles and does not break any build-time tests.
 - Be understanding, patient, and friendly; developers may need time to review
   your submissions before they can take action or respond. This does not mean
   your contribution is not valued. If your contribution has not received a