Add force-push-detection

.github/ghprcomment.yml

@@ -1,5 +1,5 @@
 - jobName: Checkstyle
-  message: |
+  message: >
     Your code currently does not meet [JabRef's code guidelines](https://devdocs.jabref.org/getting-into-the-code/guidelines-for-setting-up-a-local-workspace/intellij-13-code-style.html).
     We use [Checkstyle](https://checkstyle.sourceforge.io/) to identify issues.
     Please carefully follow [the setup guide for the codestyle](https://devdocs.jabref.org/getting-into-the-code/guidelines-for-setting-up-a-local-workspace/intellij-13-code-style.html).
@@ -8,22 +8,22 @@
     In case of issues with the import order, double check that you [activated Auto Import](https://devdocs.jabref.org/getting-into-the-code/guidelines-for-setting-up-a-local-workspace/intellij-13-code-style.html#enable-proper-import-cleanup).
     You can trigger fixing imports by pressing <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>O</kbd> to trigger [Optimize Imports](https://www.jetbrains.com/guide/tips/optimize-imports/).
 - jobName: OpenRewrite
-  message: |
+  message: >
     Your code currently does not meet JabRef's code guidelines.
     We use [OpenRewrite](https://docs.openrewrite.org/) to ensure "modern" Java coding practices.
     The issues found can be **automatically fixed**.
     Please execute the gradle task *`rewriteRun`*, check the results, commit, and push.
 
     You can check the detailed error output by navigating to your pull request, selecting the tab "Checks", section "Tests" (on the left), subsection "OpenRewrite".
 - jobName: Modernizer
-  message: |
+  message: >
     Your code currently does not meet JabRef's code guidelines.
     We use [Gradle Modernizer Plugin](https://github.com/andygoossens/gradle-modernizer-plugin#gradle-modernizer-plugin) to ensure "modern" Java coding practices.
     Please fix the detected errors, commit, and push.
 
     You can check the detailed error output by navigating to your pull request, selecting the tab "Checks", section "Tests" (on the left), subsection "Modernizer".
 - jobName: Markdown
-  message: |
+  message: >
     You modified Markdown (`*.md`) files and did not meet JabRef's rules for consistently formatted Markdown files.
     To ensure consistent styling, we have [markdown-lint](https://github.com/DavidAnson/markdownlint) in place.
     [Markdown lint's rules](https://github.com/DavidAnson/markdownlint/blob/main/doc/Rules.md#rules) help to keep our Markdown files consistent within this repository and consistent with the Markdown files outside here.
@@ -34,7 +34,18 @@
     While the PR was in progress, a new version of JabRef has been released.
     You have to merge `upstream/main` and move your entry in `CHANGELOG.md` up to the section `## [Unreleased]`.
 - jobName: 'Unit tests'
-  message: |
-    JUnit tests are failing. In the area "Some checks were not successful", locate "Tests / Unit tests (pull_request)" and click on "Details". This brings you to the test output.
+  message: >
+    JUnit tests are failing.
+    In the area "Some checks were not successful", locate "Tests / Unit tests (pull_request)" and click on "Details".
+    This brings you to the test output.
 
-    You can then run these tests in IntelliJ to reproduce the failing tests locally. We offer a quick test running howto in the section [Final build system checks](https://devdocs.jabref.org/getting-into-the-code/guidelines-for-setting-up-a-local-workspace/intellij-12-build.html#final-build-system-checks) in our setup guide.
+    You can then run these tests in IntelliJ to reproduce the failing tests locally.
+    We offer a quick test running howto in the section [Final build system checks](https://devdocs.jabref.org/getting-into-the-code/guidelines-for-setting-up-a-local-workspace/intellij-12-build.html#final-build-system-checks) in our setup guide.
+- jobName: no-force-push
+  message: >
+    Do not force-push!
+    Force push is off limits and very bad style when working together on a project.
+    ([Mainly because it is not supported well by GitHub istself.](https://github.com/orgs/community/discussions/3478))
+    Commits will be lost, comments on commits will loose their context.
+    This makes it harder to review.
+    In the end, all commits will be [squashed](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges#squash-and-merge-your-commits) either way before being merged into the `main`` branch.

.github/workflows/tests.yml

@@ -52,7 +52,6 @@ jobs:
       - name: Run checkstyle using gradle
         run: ./gradlew checkstyleMain checkstyleTest checkstyleJmh
 
-
   openrewrite:
     name: OpenRewrite
     runs-on: ubuntu-latest
@@ -372,6 +371,24 @@ jobs:
       - name: Merge Conflict finder
         uses: olivernybroe/action-conflict-finder@v4.0
 
+  no-force-push:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Check force push
+        id: force_push_check
+        run: |
+          if git cat-file -e ${{ github.event.before }} 2>/dev/null; then
+            echo "✅ Regular push detected."
+          else
+            echo "❌ Force push detected"
+            exit 1
+          fi
+
   other_than_main:
     name: Source branch is other than "main"
     runs-on: ubuntu-latest