Merge pull request #89 from bkd-mba-fbi/main-ci

.github/workflows/automerge.yml

@@ -0,0 +1,31 @@
+name: automerge
+on:
+  pull_request:
+    types:
+      - labeled
+      - unlabeled
+      - synchronize
+      - opened
+      - edited
+      - ready_for_review
+      - reopened
+      - unlocked
+  pull_request_review:
+    types:
+      - submitted
+  check_suite:
+    types:
+      - completed
+  status: {}
+jobs:
+  automerge:
+    runs-on: ubuntu-latest
+    steps:
+      - id: automerge
+        name: automerge
+        uses: "pascalgn/[email protected]"
+        env:
+          GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}"
+          MERGE_LABELS:
+            "automerge, deployment"
+            #MERGE_METHOD: "rebase"

.github/workflows/docker.yml

@@ -22,6 +22,13 @@ env:
   IMAGE_NAME: ${{ github.repository }}
 
 jobs:
+  debug:
+    runs-on: ubuntu-latest
+
+    steps:
+      - run: echo "🎉 The job was automatically triggered by a ${{ github.event_name }} event."
+      - run: echo "🎉 event info ${{ github.event.pull_request }}"
+
   prerequisites:
     runs-on: ubuntu-latest
     if: github.event.pull_request.merged == true

doc/releasing.md

@@ -29,3 +29,7 @@ Production:
 - To release & deploy to the _production_ environment running at Bedag, BKD merges the `test` branch into the `production` branch. The workflow [docker.yml](../.github/workflows/docker.yml) can usually reuse the Docker image already built for this commit and will tag it with the `production` tag. In a Gitops manner, the Bedag cluster will then deploy the `production` Image to the _production_ environment.
 
 - Hotfixes can either be made on the `production` branch (using a hotfix branch if appropriate), then cherry-picked back into the `main` branch. Or they can be made in the `main` branch, then cherry-picked into the `test`/`production` branch.
+
+## Release Instructions
+
+TODO