Automated review assignment

.github/CODEOWNERS

@@ -0,0 +1,67 @@
+# This is a comment.
+# Each line is a file pattern followed by one or more owners.
+
+# These owners will be the default owners for everything in
+# the repo. Unless a later match takes precedence,
+# @global-owner1 and @global-owner2 will be requested for
+# review when someone opens a pull request.
+
+* @zaphiro-technologies/backend-devs
+*.vi @zaphiro-technologies/labview-devs
+
+# Order is important; the last matching pattern takes the most
+# precedence. When someone opens a pull request that only
+# modifies JS files, only @js-owner and not the global
+# owner(s) will be requested for a review.
+# *.js    @js-owner #This is an inline comment.
+
+# You can also use email addresses if you prefer. They'll be
+# used to look up users just like we do for commit author
+# emails.
+# *.go [email protected]
+
+# Teams can be specified as code owners as well. Teams should
+# be identified in the format @org/team-name. Teams must have
+# explicit write access to the repository. In this example,
+# the octocats team in the octo-org organization owns all .txt files.
+# *.txt @octo-org/octocats
+
+# In this example, @doctocat owns any files in the build/logs
+# directory at the root of the repository and any of its
+# subdirectories.
+# /build/logs/ @doctocat
+
+# The `docs/*` pattern will match files like
+# `docs/getting-started.md` but not further nested files like
+# `docs/build-app/troubleshooting.md`.
+# docs/*  [email protected]
+
+# In this example, @octocat owns any file in an apps directory
+# anywhere in your repository.
+# apps/ @octocat
+
+# In this example, @doctocat owns any file in the `/docs`
+# directory in the root of your repository and any of its
+# subdirectories.
+# /docs/ @doctocat
+
+# In this example, any change inside the `/scripts` directory
+# will require approval from @doctocat or @octocat.
+# /scripts/ @doctocat @octocat
+
+# In this example, @octocat owns any file in a `/logs` directory such as
+# `/build/logs`, `/scripts/logs`, and `/deeply/nested/logs`. Any changes
+# in a `/logs` directory will require approval from @octocat.
+# **/logs @octocat
+
+# In this example, @octocat owns any file in the `/apps`
+# directory in the root of your repository except for the `/apps/github`
+# subdirectory, as its owners are left empty.
+# /apps/ @octocat
+# /apps/github
+
+# In this example, @octocat owns any file in the `/apps`
+# directory in the root of your repository except for the `/apps/github`
+# subdirectory, as this subdirectory has its own owner @doctocat
+# /apps/ @octocat
+# /apps/github @doctocat

.github/config/md-lint-config.json → .github/config/.markdownlint.json

@@ -12,7 +12,8 @@
         "allowed_elements": [
             "a",
             "img",
-            "br"
+            "br",
+            "h1"
         ]
     },
     "MD014": false,

.github/pull_request_template.md

@@ -21,5 +21,6 @@ Fixes #{bug number}  - use this specific format or issues won't be correctly lin
 - [ ] I have used a PR title that is descriptive enough for a release note.
 - [ ] I have tested these changes locally.
 - [ ] I have added appropriate tests or updated existing tests.
-- [ ] I have tested these changes on a dedicated VM or a customer VM [name of the VM]
+- [ ] I have tested these changes on a dedicated VM or a customer VM [name of
+      the VM]
 - [ ] I have added appropriate documentation or updated existing documentation.

.github/workflows/add-to-project.yaml

@@ -0,0 +1,15 @@
+name: Project Management
+on:
+  issues:
+    types:
+      - labeled
+  pull_request:
+    branches: [ "main" ]
+    types:
+      - labeled
+  workflow_call:
+
+jobs:
+  add-to-project:
+    uses: zaphiro-technologies/github-workflows/.github/workflows/add-to-project.yaml@main
+    secrets: inherit

.github/workflows/check-pr.yaml

@@ -0,0 +1,17 @@
+name: Validate PR
+
+on:
+  pull_request:
+    branches: [ "main" ]
+    types:
+      - opened
+      - reopened
+      - edited
+      - synchronize
+      - labeled
+      - unlabeled
+
+jobs:
+ check-pr:
+    uses: zaphiro-technologies/github-workflows/.github/workflows/check-pr.yaml@main
+    secrets: inherit

.github/workflows/markdown.yaml

@@ -0,0 +1,12 @@
+name: Markdown Check
+
+on:
+  push:
+    branches: [ "main" ]
+  pull_request:
+    branches: [ "main" ]
+
+jobs:
+  markdown-checker:
+    uses: zaphiro-technologies/github-workflows/.github/workflows/markdown.yaml@main
+    secrets: inherit

profile/README.MD

@@ -1,8 +1,10 @@
-<img src="https://zaphiro.ch/wp-content/uploads/2020/02/zaphiro-technologies-smart-grid-logo-color.svg" alt="Zaphiro
-Technologies" width="300">
+<h1>
+<img src="https://zaphiro.ch/wp-content/uploads/2020/02/zaphiro-technologies-smart-grid-logo-color.svg"
+alt="Zaphiro Technologies" width="300"/>
+</h1>
 
-Zaphiro is a leading Swiss deep tech company in Smart Grid solutions.
-We help energy players optimize power grid monitoring and automation through
-software solutions integrated with proprietary or third-party hardware.
+Zaphiro is a leading Swiss deep tech company in Smart Grid solutions. We help
+energy players optimize power grid monitoring and automation through software
+solutions integrated with proprietary or third-party hardware.
 
 Find out more on our [web site](https://zaphiro.ch).

workflow-templates/check-pr.yaml

@@ -1,9 +1,5 @@
 name: Validate PR
 
-concurrency:
-  group: ${{ github.ref_name }}-validate-pr
-  cancel-in-progress: true
-
 on:
   pull_request:
     branches: [ $default-branch ]
@@ -18,4 +14,4 @@ on:
 jobs:
  check-pr:
     uses: zaphiro-technologies/github-workflows/.github/workflows/check-pr.yaml@main
-    secrets: inherit
+    secrets: inherit