inno-devops-labs · KsAKarpeeva73 · Feb 4, 2026 · Feb 4, 2026 · Feb 4, 2026 · Feb 4, 2026
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
@@ -0,0 +1,12 @@
+## Goal
+Finish Lab 1 by setting up SSH commit signing and a pull request template.
+
+## Changes
+- Enabled SSH-based commit signing
+- Added lab report and screenshots
+- Introduced a standard PR template
+
+## Testing
+- [ ] Project builds and runs successfully
+- [ ] Commits are signed and verified
+- [ ] Documentation is complete and updated
diff --git a/.github/workflows/lab3.yml b/.github/workflows/lab3.yml
@@ -0,0 +1,49 @@
+name: Lab 3 CI
+
+on:
+  push:
+    branches:
+      - feature/lab3
+  workflow_dispatch:
+
+jobs:
+  basic-info:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Print basic info
+        run: |
+          echo "Hello from GitHub Actions!"
+          date
+          echo "Actor: $GITHUB_ACTOR"
+          echo "Ref: $GITHUB_REF"
+          echo "SHA: $GITHUB_SHA"
+          uname -a
+
+      - name: System information
+        run: |
+          echo "=== SYSTEM INFO ==="
+          echo "--- OS / Kernel ---"
+          uname -a
+          cat /etc/os-release || true
+
+          echo "--- CPU ---"
+          nproc
+          lscpu || true
+          cat /proc/cpuinfo | head -n 30 || true
+
+          echo "--- Memory ---"
+          free -h || true
+          cat /proc/meminfo | head -n 20 || true
+
+          echo "--- Disk ---"
+          df -h
+          lsblk || true
+
+          echo "--- GitHub runner env ---"
+          echo "RUNNER_OS=$RUNNER_OS"
+          echo "RUNNER_ARCH=$RUNNER_ARCH"
+          echo "RUNNER_NAME=$RUNNER_NAME"
+          echo "RUNNER_TEMP=$RUNNER_TEMP"
+          echo "GITHUB_WORKFLOW=$GITHUB_WORKFLOW"
+          echo "GITHUB_RUN_ID=$GITHUB_RUN_ID"
+          echo "GITHUB_RUN_NUMBER=$GITHUB_RUN_NUMBER"
diff --git a/.gitignore b/.gitignore
@@ -0,0 +1,164 @@
+### Python template
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/latest/usage/project/#working-with-version-control
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+.idea/
+
diff --git a/demo.txt b/demo.txt
@@ -0,0 +1 @@
+base
diff --git a/labs/screenshots/img.png b/labs/screenshots/img.png
diff --git a/labs/screenshots/img_1.png b/labs/screenshots/img_1.png
diff --git a/labs/screenshots/img_10.png b/labs/screenshots/img_10.png
diff --git a/labs/screenshots/img_11.png b/labs/screenshots/img_11.png
diff --git a/labs/screenshots/img_12.png b/labs/screenshots/img_12.png
diff --git a/labs/screenshots/img_13.png b/labs/screenshots/img_13.png
diff --git a/labs/screenshots/img_14.png b/labs/screenshots/img_14.png
diff --git a/labs/screenshots/img_15.png b/labs/screenshots/img_15.png
diff --git a/labs/screenshots/img_16.png b/labs/screenshots/img_16.png
diff --git a/labs/screenshots/img_2.png b/labs/screenshots/img_2.png
diff --git a/labs/screenshots/img_3.png b/labs/screenshots/img_3.png
diff --git a/labs/screenshots/img_4.png b/labs/screenshots/img_4.png
diff --git a/labs/screenshots/img_5.png b/labs/screenshots/img_5.png
diff --git a/labs/screenshots/img_6.png b/labs/screenshots/img_6.png
diff --git a/labs/screenshots/img_7.png b/labs/screenshots/img_7.png
diff --git a/labs/screenshots/img_8.png b/labs/screenshots/img_8.png
diff --git a/labs/screenshots/img_9.png b/labs/screenshots/img_9.png
diff --git a/labs/screenshots/lab_8_new/alert_settings.png b/labs/screenshots/lab_8_new/alert_settings.png
diff --git a/labs/screenshots/lab_8_new/api_check_config.png b/labs/screenshots/lab_8_new/api_check_config.png
diff --git a/labs/screenshots/lab_8_new/browser_check_config.png b/labs/screenshots/lab_8_new/browser_check_config.png
diff --git a/labs/screenshots/lab_8_new/browser_check_result.png b/labs/screenshots/lab_8_new/browser_check_result.png
diff --git a/labs/screenshots/lab_8_new/dashboard_overview.png b/labs/screenshots/lab_8_new/dashboard_overview.png
diff --git a/labs/screenshots/lab_9_new/trivy_critical_findings.png b/labs/screenshots/lab_9_new/trivy_critical_findings.png
diff --git a/labs/screenshots/lab_9_new/zap_medium_alerts.png b/labs/screenshots/lab_9_new/zap_medium_alerts.png
diff --git a/labs/screenshots/lab_9_new/zap_report_overview.png b/labs/screenshots/lab_9_new/zap_report_overview.png
diff --git a/labs/submission1.md b/labs/submission1.md
@@ -0,0 +1,61 @@
+# Lab 1
+
+## Task 1: SSH Commit Signature Verification
+
+**Summary of the benefits of signing commits**
+
+My answer:
+
+Signing Git commits shows that the commit was really created by you. A digital signature is added to the commit using your private key.
+
+First, it confirms the author. A signed commit proves that the code was made by the real owner of the account, not someone else using the same name or email. On platforms like GitHub, this is shown with a *Verified* badge, which helps others trust the commit.
+
+Second, it protects the commit from changes. The signature checks that the code, message, and author information were not modified after the commit was created. If anything is changed, the signature becomes invalid.
+
+Commit signing is important for project security, especially in team and open-source projects. It helps prevent fake commits and makes it clear who made each change.
+
+In short, signing commits is a simple way to make your project history more secure and trustworthy.
+
+**Evidence of successful SSH key setup and signed commit.**
+
+  ![SSH Key Setup](screenshots/img.png)
+
+**Question: "Why is commit signing important in DevOps workflows?"**
+
+
+My answer:
+
+In DevOps workflows, automation is widely used. CI/CD pipelines automatically build and deploy code.
+If an attacker pretends to be a developer and pushes harmful code, the pipeline may deploy it to production.
+Commit signing helps prevent this. Pipelines can be set to accept only commits signed with trusted keys.
+This adds an extra layer of protection to the software supply chain.
+
+
+**Screenshots or verification of the "Verified" badge on GitHub.**
+
+  ![Verified Badge](screenshots/img_1.png)
+
+
+## Task 2: PR Template and Checklist
+
+**Screenshot of PR template filling the desc**
+
+  ![PR Template](screenshots/img_3.png)
+
+**Evidence that .github/pull_request_template.md exists on main branch.**
+
+  The file exists at `.github/pull_request_template.md`.
+  ![File in .github folder](screenshots/img_2.png)
+
+
+**Analysis of how PR templates improve collaboration**
+
+PR templates make the code review process more organized and easier to follow.
+
+1. **Clear information:** Each pull request includes a clear goal and list of changes, so reviewers immediately understand what was done.
+2. **Same structure:** All contributors use the same format, which makes reviews faster and more consistent.
+3. **Better quality:** Checklists remind authors to test their code and update documentation before opening a PR, which reduces extra comments and rework.
+
+**Challenges during setup**
+
+The main issue was the setup order. The PR template must be added and pushed to the `main` branch before creating a pull request. If this is not done, GitHub does not apply the template automatically.