Merge branch 'main' into feature/OP-2105/dependabot

.github/CODEOWNERS

@@ -1 +1 @@
-*   @platform/platform
+*   @RiskIdent/platform

.github/workflows/eclint.yml

@@ -5,8 +5,7 @@ on:
 
 jobs:
   eclint:
-    runs-on:
-      group: ephemeral_runners
+    runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
 

.github/workflows/markdownlint.yml

@@ -8,4 +8,13 @@ on:
 
 jobs:
   markdownlint:
-    uses: platform/reusable-workflows/.github/workflows/markdownlint.yml@main
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+
+      - name: markdownlint
+        uses: reviewdog/action-markdownlint@v0
+        with:
+          github_token: ${{ secrets.GITHUB_TOKEN }}
+          reporter: github-pr-review
+          fail_on_error: true

.github/workflows/yamllint.yml

@@ -10,8 +10,7 @@ on:
 
 jobs:
   yamllint:
-    runs-on:
-      group: ephemeral_runners
+    runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
 

README.md

@@ -14,7 +14,7 @@ internal Jira. We expose `ri-forward-webhook`, and with the additional
 webhook signature validation we can feel safe on not letting bad actors
 sending arbitrary requests to our precious Jira.
 
-In addition, in the [iac repo](https://github.2rioffice.com/platform/iac),
+In addition, in our infrastructure as code repo,
 we use [Cloudflare Tunnels](https://www.cloudflare.com/products/tunnel/)
 to expose `ri-forward-webhook`, so that nothing else in our Kubernetes cluster
 is accidentally exposed to the Internet.
@@ -66,5 +66,5 @@ go run .
 ## Building
 
 ```bash
-podman build . -t docker-riskident.2rioffice.com/platform/ri-forward-webhook
+podman build . -t ghcr.io/riskident/ri-forward-webhook
 ```

go.mod

@@ -1,4 +1,4 @@
-module github.2rioffice.com/platform/ri-forward-webhook
+module github.com/RiskIdent/ri-forward-webhook
 
 go 1.21.1