inital commit with current files

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,65 @@
+name: 🐞 Bug report
+description: File a bug/issue to help us improve
+title: "[BUG]"
+labels: [bug]
+assignees: [MartinPankraz]
+body:
+  - type: checkboxes
+    attributes:
+      label: Is there an existing issue for this?
+      description: Please search to see if an issue already exists for the bug you encountered.
+      options:
+        - label: I have searched the existing issues
+          required: true
+  - type: dropdown
+    id: area
+    attributes:
+      label: What type of issue are you facing
+      description: What type of issue are you facing?
+      options:
+        - bug report
+        - documentation issue or request
+        - regression (a behavior that used to work and stopped in a new version)
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Describe the bug
+      description: Provide a clear and concise description of what the bug is.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Expected Behavior
+      description: A concise description of what you expected to happen.
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Steps To Reproduce
+      description: Steps to reproduce the behavior.
+      placeholder: |
+        1. Go to '...'
+        2. Click on '....'
+        3. Scroll down to '....'
+        4. See error
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Add screenshots to help explain your problem
+      description: |
+        If applicable, add screenshots to help explain your problem.
+
+        Tip: You can attach images or files by clicking this area to highlight it and then dragging files in.
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Additional context
+      description: |
+        Add any other context like links or references about the problem here. Anything that will give us more context about the issue you are encountering!
+
+        Tip: You can attach images or files by clicking this area to highlight it and then dragging files in.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,46 @@
+name: 💡Feature request
+description: Suggest an idea for this project
+title: "[FEATURE]"
+labels: [enhancement]
+assignees: [MartinPankraz]
+body:
+  - type: dropdown
+    attributes:
+      label: What area do you want to see improved?
+      description: Specify the main area that you want to see improved.
+      options:
+        - app code
+        - documentation
+        - infrastructure setup
+        - developer experience (GitHub CodeSpaces etc.)
+        - other
+    validations:
+      required: true
+  - type: textarea
+    id: area
+    attributes:
+      label: Is your feature request related to a problem? Please describe.
+      description: Provide a clear and concise description of what the problem is e.g., I'm always frustrated when [...]
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Describe the solution you'd like
+      description: A clear and concise description of what you want to happen.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Describe alternatives you've considered
+      description: A clear and concise description of any alternative solutions or features you've considered.
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Additional context
+      description: |
+        Add any other context like links or references about the problem here. Anything that will give us more context about the issue you are encountering!
+
+        Tip: You can attach images or files by clicking this area to highlight it and then dragging files in.
+    validations:
+      required: false

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,36 @@
+## Purpose
+<!-- Describe the intention of the changes being proposed. What problem does it solve or functionality does it add? -->
+* ...
+
+## Does this introduce a breaking change?
+<!-- Mark one with an "x". -->
+```
+[ ] Yes
+[ ] No
+```
+
+## Pull Request Type
+What kind of change does this Pull Request introduce?
+
+<!-- Please check the one that applies to this PR using "x". -->
+```
+[ ] Bugfix
+[ ] Feature
+[ ] Code style update (formatting, local variables)
+[ ] Refactoring (no functional changes, no api changes)
+[ ] Documentation content changes
+[ ] Other... Please describe:
+```
+
+## How to Test
+* Test the code
+<!-- Add steps to run the tests suite and/or manually test -->
+```
+```
+
+## What to Check
+Verify that the following are valid
+* ...
+
+## Other Information
+<!-- Add any other helpful information that may be needed here. -->

.github/dependabot.yml

@@ -0,0 +1,17 @@
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      # Check for updates to GitHub Actions once a week on Monday
+      interval: "weekly"
+      day: "monday"
+  - package-ecosystem: "pip"
+    directory: /backend-printing
+    schedule:
+      interval: "weekly"
+      day: "monday"
+    groups:
+      python-packages:
+        patterns:
+          - "*"

.github/workflows/links-watcher.yml

@@ -0,0 +1,44 @@
+name: Periodic Link Checker
+
+on:
+  schedule:
+    - cron: "0 23 * * *"
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  issues: write
+
+jobs:
+  link-checker:
+    runs-on: ubuntu-latest
+    steps:
+      - name: "Checkout source code"
+        uses: actions/checkout@v4
+      - name: Link Checker
+        id: lychee
+        uses: lycheeverse/lychee-action@v1.10.0
+        with:
+          args: --verbose --no-progress --max-concurrency 2 --exclude-link-local --exclude-loopback './**/*.md' --exclude portal.azure.com --exclude developers.sap.com --exclude fully.qualified.domainname
+          output: ./lychee/out.md
+          fail: true
+        env:
+          GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
+      - name: Find existing issue
+        id: find_issue
+        uses: micalevisk/last-issue-action@v2
+        if: failure()
+        with:
+          state: open
+          labels: |
+            broken link
+            automated issue
+      - name: Create or update issue for broken links
+        uses: peter-evans/create-issue-from-file@v5
+        if: failure()
+        with:
+          title: Link Checker Report
+          # If issue number is empty a new issue gets created
+          issue-number: ${{ steps.find_issue.outputs.issue-number }}
+          content-filepath: ./lychee/out.md
+          labels: broken link, automated issue

.github/workflows/pull-request.yml

@@ -0,0 +1,40 @@
+# This is a pull request workflow. It will run linting and unit tests on the backend-printing directory.
+
+name: Pull Request Workflow
+
+# Controls when the workflow will run
+on:
+  # Triggers the workflow on push or pull request events but only for the "main" branch
+  pull_request:
+    branches: [ "main" ]
+    types: [ assigned, opened, synchronize, reopened ]
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+# A workflow run is made up of one or more jobs that can run sequentially or in parallel
+jobs:
+  # This workflow contains a single job called "build"
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v2
+
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: "3.10"
+
+      - name: Install dependencies
+        working-directory: backend-printing
+        run: pip install -r requirements.txt
+
+      - name: Lint with pylint and flake8
+        working-directory: backend-printing
+        run: pylint --fail-on=E --fail-under=9 --disable=I,R,W,C $(git ls-files '*.py') --rcfile=./.pylintrc
+
+      - name: Run unit tests
+        working-directory: backend-printing
+        run: pytest ./tests