chore: update prepare-commit-msg hook from kull

Author: xeruf

.dev/githooks/prepare-commit-msg

@@ -1,13 +1,10 @@
-#!/bin/sh
+#!/bin/bash
 #
-# This hook adds a comment for guidance about the commit message
-# format on top of the default commit message.
+# This hook adds guidance about the commit message format
+# on top of the default commit message.
 #
-# Called by "git commit" with the name of the file that has the
-# commit message, followed by the description of the commit
-# message's source.  The hook's purpose is to edit the commit
-# message file.  If the hook fails with a non-zero status,
-# the commit is aborted.
+# Called by "git commit" with the name of the file that has the commit message,
+# followed by the description of the commit message's source.
 #
 # To enable this hook, set the hooksPath in git:
 # git config core.hooksPath .dev/githooks
@@ -16,15 +13,37 @@ COMMIT_MSG_FILE=$1
 COMMIT_SOURCE=$2
 SHA1=$3
 
+scopes_file=".dev/scopes.txt"
+test -r $scopes_file &&
+  scopes="$(cat "$scopes_file" | sed '/^\(#.*\|\)$/d' | sed ':a;N;s/\n/, /g;ta')"
+
 beginswith() { case $2 in "$1"*) true;; *) false;; esac; }
 
+# https://mincong.io/2019/07/23/prepare-commit-message-using-git-hook
+# Only add custom message when there is no commit source ($COMMIT_SOURCE is empty).
+# Otherwise, keep the default message proposed by Git.
+# Possible commit sources: message, template, merge, squash or commit.
+# See https://git-scm.com/docs/githooks
 original=$(cat "$COMMIT_MSG_FILE")
-if beginswith $'\n#' "$original"; then
-    {
-        printf "\n\n# Please enter the message in the format\n"
-        echo "# <type>(<scope>): <description>"
-        echo "# Possible types: fix, feat, docs, style, refactor, test, chore, rework, release"
-        printf "# For details see https://www.notion.so/softwarechallenge/Git-217333329ea64db5b2cc8bbbaf79db87"
-        echo "$original"
-    } > "$COMMIT_MSG_FILE"
+if test -z "$COMMIT_SOURCE"
+then
+  # Find common path prefix of changed files
+  path=$(while read file
+    do test -z "$count" && common="$file" && count=$(expr length "$file") ||
+      while expr substr "$file" $count 1 != substr "$common" $count 1 >/dev/null; do let count--; done
+    done <<<"$(git -P diff --cached --name-only -r)" &&
+      expr substr "$common" 1 "$count")
+  {
+    # Infer type & scope from changed files
+    expr "$path" : "gradle" >/dev/null &&
+      printf "chore(gradle): " ||
+      printf "fix(%s): " $path
+
+    printf "\n\n# Please enter the message in the format\n"
+    echo "# <type>(<scope>): <description>"
+    echo "# Possible types: fix, feat, docs, style, refactor, test, chore, rework, release"
+    test -n "$scopes" && echo "# Allowed scopes: $scopes"
+    printf "# For details see https://www.notion.so/softwarechallenge/Git-217333329ea64db5b2cc8bbbaf79db87"
+    echo "$original"
+  } > "$COMMIT_MSG_FILE"
 fi

CHANGELOG.md

@@ -10,7 +10,7 @@ The version should always be in sync with the [GUI](https://github.com/software-
   A `y` version of 0 marks the beta of the current year
   and likely contains breaking changes between patches.
 
-### [23.0.1](https://github.com/software-challenge/backend/commits/23.0.0) Proper Penguins - 2022-07-28
+### [23.0.1](https://github.com/software-challenge/backend/commits/23.0.1) Proper Penguins - 2022-08-06
 - Proper rule implementation for Penguins with some helpers
 
 ### [23.0.0](https://github.com/software-challenge/backend/commits/23.0.0) Rough Penguins - 2022-07-28

CONTRIBUTING.md

@@ -30,7 +30,7 @@ ansonsten (gerade bei experimentier-Branches) ein squash merge,
 wobei der Titel des Pull Requests der Commit-Message entsprechen sollte.
 
 Detaillierte Informationen zu unserem Kollaborations-Stil
-findet ihr in der [Kull Konvention](https://xerus2000.github.io/kull).
+findet ihr in der [Kull Konvention](https://kull.jfischer.org).
 
 ## Build
 
@@ -75,4 +75,4 @@ In IntelliJ kann man das Projekt bequem via Gradle importieren,
 wodurch alle Module und Bibliotheken automatisch geladen werden.
 
 Dann können Gradle-Tasks auch direkt in IntelliJ vom Gradle-Werkzeugfenster ausgeführt werden;
-dieses befindet sich normalerweise in der rechten Andockleiste.
+dieses befindet sich normalerweise in der rechten Andockleiste.