inno-devops-labs · zv3zdochka · Feb 3, 2026 · Feb 3, 2026 · Feb 3, 2026 · Feb 3, 2026
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
@@ -0,0 +1,10 @@
+## Goal
+<!-- Briefly describe the purpose of this PR -->
+
+## Changes
+<!-- List the key changes made -->
+
+## Testing
+- [ ] Code compiles/runs without errors
+- [ ] Signed commits verified
+- [ ] Documentation updated
diff --git a/.github/workflows/lab3.yml b/.github/workflows/lab3.yml
@@ -0,0 +1,58 @@
+name: Lab3 CI
+
+on:
+  push:
+  workflow_dispatch:
+
+jobs:
+  info:
+    name: Basic info
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repo
+        uses: actions/checkout@v4
+
+      - name: Print workflow context
+        run: |
+          echo "Event: ${{ github.event_name }}"
+          echo "Branch ref: ${{ github.ref }}"
+          echo "Commit SHA: ${{ github.sha }}"
+          echo "Repository: ${{ github.repository }}"
+          echo "Actor: ${{ github.actor }}"
+
+      - name: Print OS basics
+        run: |
+          uname -a
+          git --version
+
+      - name: Gather system information
+        run: |
+          echo "===== OS / Kernel ====="
+          uname -a
+          cat /etc/os-release || true
+
+          echo "===== CPU ====="
+          nproc
+          lscpu || true
+
+          echo "===== Memory ====="
+          free -h || true
+
+          echo "===== Disk ====="
+          df -h || true
+
+          echo "===== Network ====="
+          ip -br a || true
+
+          echo "===== Tooling ====="
+          git --version
+          python --version || true
+
+  second-job:
+    name: Dependent job
+    runs-on: ubuntu-latest
+    needs: info
+    steps:
+      - name: Confirm dependency
+        run: |
+          echo "Second job after first (needs: info)"
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
diff --git a/labs/screenshots/lab_1/lab_1_1.png b/labs/screenshots/lab_1/lab_1_1.png
diff --git a/labs/screenshots/lab_1/lab_1_2.png b/labs/screenshots/lab_1/lab_1_2.png
diff --git a/labs/screenshots/lab_1/lab_1_3.png b/labs/screenshots/lab_1/lab_1_3.png
diff --git a/labs/screenshots/lab_1/lab_1_4.png b/labs/screenshots/lab_1/lab_1_4.png
diff --git a/labs/screenshots/lab_1/lab_1_5.png b/labs/screenshots/lab_1/lab_1_5.png
diff --git a/labs/screenshots/lab_2/lab_2_1.png b/labs/screenshots/lab_2/lab_2_1.png
diff --git a/labs/screenshots/lab_2/lab_2_10.png b/labs/screenshots/lab_2/lab_2_10.png
diff --git a/labs/screenshots/lab_2/lab_2_11.png b/labs/screenshots/lab_2/lab_2_11.png
diff --git a/labs/screenshots/lab_2/lab_2_12.png b/labs/screenshots/lab_2/lab_2_12.png
diff --git a/labs/screenshots/lab_2/lab_2_13.png b/labs/screenshots/lab_2/lab_2_13.png
diff --git a/labs/screenshots/lab_2/lab_2_14.png b/labs/screenshots/lab_2/lab_2_14.png
diff --git a/labs/screenshots/lab_2/lab_2_15.png b/labs/screenshots/lab_2/lab_2_15.png
diff --git a/labs/screenshots/lab_2/lab_2_16.png b/labs/screenshots/lab_2/lab_2_16.png
diff --git a/labs/screenshots/lab_2/lab_2_2.png b/labs/screenshots/lab_2/lab_2_2.png
diff --git a/labs/screenshots/lab_2/lab_2_3.png b/labs/screenshots/lab_2/lab_2_3.png
diff --git a/labs/screenshots/lab_2/lab_2_4.png b/labs/screenshots/lab_2/lab_2_4.png
diff --git a/labs/screenshots/lab_2/lab_2_5.png b/labs/screenshots/lab_2/lab_2_5.png
diff --git a/labs/screenshots/lab_2/lab_2_6.png b/labs/screenshots/lab_2/lab_2_6.png
diff --git a/labs/screenshots/lab_2/lab_2_7.png b/labs/screenshots/lab_2/lab_2_7.png
diff --git a/labs/screenshots/lab_2/lab_2_8.png b/labs/screenshots/lab_2/lab_2_8.png
diff --git a/labs/screenshots/lab_2/lab_2_9.png b/labs/screenshots/lab_2/lab_2_9.png
diff --git a/labs/screenshots/lab_3/lab_3_0.png b/labs/screenshots/lab_3/lab_3_0.png
diff --git a/labs/screenshots/lab_3/lab_3_1.png b/labs/screenshots/lab_3/lab_3_1.png
diff --git a/labs/screenshots/lab_3/lab_3_10.png b/labs/screenshots/lab_3/lab_3_10.png
diff --git a/labs/screenshots/lab_3/lab_3_2.png b/labs/screenshots/lab_3/lab_3_2.png
diff --git a/labs/screenshots/lab_3/lab_3_3.png b/labs/screenshots/lab_3/lab_3_3.png
diff --git a/labs/screenshots/lab_3/lab_3_4.png b/labs/screenshots/lab_3/lab_3_4.png
diff --git a/labs/screenshots/lab_3/lab_3_5.png b/labs/screenshots/lab_3/lab_3_5.png
diff --git a/labs/screenshots/lab_3/lab_3_6.png b/labs/screenshots/lab_3/lab_3_6.png
diff --git a/labs/screenshots/lab_3/lab_3_7.png b/labs/screenshots/lab_3/lab_3_7.png
diff --git a/labs/screenshots/lab_3/lab_3_8.png b/labs/screenshots/lab_3/lab_3_8.png
diff --git a/labs/screenshots/lab_3/lab_3_9.png b/labs/screenshots/lab_3/lab_3_9.png
diff --git a/labs/screenshots/lab_4/lab_4_1.png b/labs/screenshots/lab_4/lab_4_1.png
diff --git a/labs/submission1.md b/labs/submission1.md
@@ -0,0 +1,62 @@
+# Lab 1
+
+## Task 1: SSH Commit Signature Verification
+
+* A short summary explaining the benefits of signing commits.
+
+Signing your Git commits proves you are the actual author. It attaches a digital signature, generated by your private
+key, to the commit itself. This serves several important purposes.
+
+First, it provides verification. It confirms that the commit truly came from you and not someone else using your name
+and email address. On platforms like GitHub or GitLab, this is shown with a "Verified" badge next to the commit, making
+trusted contributions easy to spot.
+
+Second, it ensures integrity. The signature also confirms that the commit—its code, message, author, and date—has not
+been tampered with after you created it. If any part is altered, the verification will fail.
+
+This practice is a cornerstone of software supply chain security, particularly for open-source projects and teams. It
+prevents malicious actors from injecting code while pretending to be a trusted contributor. For organizations, it can be
+a requirement for security compliance and audit trails, as it creates a non-repudiable record of who changed what and
+when.
+
+In short, signing commits is a straightforward technical step that establishes a chain of trust for your code's history.
+It moves the project from "this commit claims to be from person X" to "this commit is verified to be from person X."
+
+* Evidence of successful SSH key setup and signed commit.
+
+  ![SSH Key Setup](screenshots/lab_1/lab_1_2.png)
+  ![Signed Commit](screenshots/lab_1/lab_1_3.png)
+*
+* Answer: "Why is commit signing important in DevOps workflows?"
+
+  In DevOps workflows, automation plays a huge role. CI/CD pipelines automatically build and deploy code.
+  If a hacker impersonates a developer and pushes malicious code, the pipeline might deploy it to production.
+  Commit signing prevents this: pipelines can be configured to reject any commits that are not signed by a trusted key.
+  This protects the software supply chain.
+
+* Screenshots or verification of the "Verified" badge on GitHub.
+
+  ![Verified Badge](screenshots/lab_1/lab_1_1.png)
+
+
+## Task 2: PR Template & Checklist
+
+* Screenshot of PR template auto-filling the description.
+
+  ![PR Template Logic](screenshots/lab_1/lab_1_5.png)
+
+* Evidence that .github/pull_request_template.md exists on main branch.
+
+  The file exists at `.github/pull_request_template.md` in the repository root.
+  ![File in .github folder](screenshots/lab_1/lab_1_4.png)
+
+* Analysis of how PR templates improve collaboration.
+
+  PR templates standardize the code review process. 
+  1. **Clarity:** They ensure every PR has a clear goal and description of changes, so reviewers don't have to guess.
+  2. **Consistency:** All developers follow the same format.
+  3. **Quality Assurance:** The checklist reminds the author to perform essential checks (like testing or documentation) before requesting a review, reducing back-and-forth communication.
+
+* Note any challenges encountered during setup.
+
+  The main challenge was the order of operations: the template file must be pushed to the `main` branch *before* creating the Pull Request, otherwise GitHub does not load it automatically.