chore: common .github files (#14)

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,14 @@
+<!--
+
+NOTE
+NOTE In most cases, you should create an issue first, and only then
+NOTE a pull request.  Please see the contribution guidelines for
+NOTE further information.  In particular related to conventional
+NOTE commit messages.
+NOTE
+
+The title should have the following format:
+
+  <type>: description (#<issue>)
+
+-->

.github/workflows/add-issue-to-project.yml

@@ -0,0 +1,27 @@
+name: add issues to project
+
+on:
+  issues:
+    types:
+      - opened
+
+jobs:
+  add-to-project:
+    name: add issue to project
+    runs-on: ubuntu-latest
+    steps:
+      - name: register bug/needs-triage with bug tracker project
+        uses: actions/add-to-project@v0.5.0
+        with:
+          project-url: https://github.com/orgs/varfish-org/projects/3
+          github-token: ${{ secrets.BOT_TOKEN }}
+          labeled: bug, needs-triage
+          label-operator: OR
+
+      - name: register bug/enhancement issues with release planning project
+        uses: actions/add-to-project@v0.5.0
+        with:
+          project-url: https://github.com/orgs/varfish-org/projects/2
+          labeled: bug, needs-triage, enhancement
+          label-operator: OR
+          github-token: ${{ secrets.BOT_TOKEN }}

.github/workflows/add-pr-to-project.yml

@@ -0,0 +1,18 @@
+name: add needs-review pull requests to projects
+
+on:
+  pull_request:
+    types:
+      - labeled
+
+jobs:
+  add-to-project:
+    name: Add pull request to project
+    runs-on: ubuntu-latest
+    steps:
+      - name: register pull requests with release planning project
+        uses: actions/add-to-project@v0.5.0
+        with:
+          project-url: https://github.com/orgs/varfish-org/projects/2
+          github-token: ${{ secrets.BOT_TOKEN }}
+          labeled: needs-review