chore(workflow): add PR template, commit title enforcement, issue link check, and contribution guidelines [skip ci]

Author: phil-man-git-hub

.github/pull_request_template.md

@@ -1,4 +1,37 @@
-<!-- 
+# Pull Request Template for LOGIK-PROJEKT
+
+## Title
+<!--
+  - Use format: [TYPE] Short description (#issue-number)
+  - Example: [FEATURE] Add desktop app automation (#42)
+-->
+
+## Linked Issue
+<!--
+  - Link to the relevant issue using: Closes #issue-number
+  - Example: Closes #42
+-->
+
+## Description
+<!--
+  - Briefly describe the purpose and context of this PR.
+  - Include any relevant background, motivation, or design decisions.
+-->
+
+## Checklist
+- [ ] PR title follows required format
+- [ ] Linked to a relevant issue (Closes #...)
+- [ ] All new and updated code is documented
+- [ ] Tests added or updated (if applicable)
+- [ ] CI checks pass (lint, tests, workflows)
+- [ ] Changelog and release notes updated
+- [ ] No large, unrelated changes (PR is focused)
+- [ ] All reviewers added
+
+## Additional Notes
+<!--
+  - Add any extra context, screenshots, or migration notes here.
+--><!-- 
 Thank you for your Pull Request! 
 Please fill out this template to help reviewers understand your changes.
 Delete sections that aren't applicable to your PR.

.github/workflows/conventional-commit-title.yml

@@ -0,0 +1,43 @@
+name: Conventional Commit Title Check
+
+on:
+  pull_request:
+    types: [opened, edited, synchronize]
+  push:
+    branches:
+      - prod-2027.0.0
+      - release-*
+
+jobs:
+  commit-title-lint:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+      - name: Validate PR title (Conventional Commits)
+        if: github.event_name == 'pull_request'
+        uses: amannn/action-semantic-pull-request@v5
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          types: |-
+            feat
+            fix
+            docs
+            style
+            refactor
+            perf
+            test
+            build
+            ci
+            chore
+            revert
+          scopes: ''
+          requireScope: false
+          subjectPattern: '^[A-Z].*'
+          wip: false
+      - name: Validate commit messages (Conventional Commits)
+        if: github.event_name == 'push'
+        uses: wagoid/commitlint-github-action@v6
+        with:
+          configFile: .github/commitlint.config.js

.github/workflows/require-issue-link.yml

@@ -0,0 +1,19 @@
+name: Require Issue Link in PR
+
+on:
+  pull_request:
+    types: [opened, edited, synchronize]
+
+jobs:
+  require-issue-link:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check PR description for issue link
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const prBody = github.context.payload.pull_request.body || '';
+            const issueLinkPattern = /(Closes|Fixes)\s+#\d+/i;
+            if (!issueLinkPattern.test(prBody)) {
+              core.setFailed('PR description must include "Closes #N" or "Fixes #N" to link an issue.');
+            }

CONTRIBUTING.md

@@ -0,0 +1,33 @@
+# Contributing to LOGIK-PROJEKT
+
+Thank you for your interest in contributing! To keep our codebase maintainable and our review process efficient, please follow these guidelines:
+
+## Pull Request Guidelines
+
+- **Break large changes into focused PRs:**
+  - Submit small, logically grouped changes rather than large, multi-purpose PRs.
+  - Each PR should address a single feature, bugfix, or refactor whenever possible.
+  - Large changesets are harder to review, test, and merge. If your work is broad, split it into multiple PRs and reference them in each description.
+
+- **PR Title and Issue Linking:**
+  - Use the required PR title format (see PULL_REQUEST_TEMPLATE.md).
+  - Link to a relevant issue using "Closes #N" or "Fixes #N" in the PR description.
+
+- **Checklist Before Submitting:**
+  - Ensure all code is documented and tested.
+  - Update changelogs and release notes as needed.
+  - Confirm CI checks pass before requesting review.
+
+## General Contribution Process
+
+1. Fork the repository and create your feature branch from `prod-2027.0.0` or the latest release branch.
+2. Make your changes, keeping each PR focused and atomic.
+3. Run tests and linters locally before pushing.
+4. Open a pull request and fill out all required template sections.
+5. Address review feedback promptly and keep PRs up to date with the base branch.
+
+For more details, see the PR template and workflows in `.github/`.
+
+---
+
+If you have questions, open an issue or contact the maintainers.