Feature/lab8

.github/pull_request_template.md

@@ -0,0 +1,13 @@
+## Goal
+- What does this PR accomplish?
+
+## Changes
+- What was modified?
+
+## Testing
+- What was modified?
+
+### Checklist:
+- [ ] Clear title and description.
+- [ ] Documentation/README updated if needed.
+- [ ] No secrets or large temporary files.

.github/workflows/github-actions-demo.yml

@@ -0,0 +1,44 @@
+name: GitHub Actions Demo
+run-name: ${{ github.actor }} is testing out GitHub Actions 🚀
+
+on:
+  workflow_dispatch:
+
+jobs:
+  Explore-GitHub-Actions:
+    runs-on: ubuntu-latest
+    steps:
+      - run: echo "Triggered by ${{ github.event_name }}"
+
+      - name: Check out repository code
+        uses: actions/checkout@v5
+
+      - name: System info
+        run: |
+          echo ""
+          echo "========================================"
+          echo "SYSTEM INFORMATION"
+          echo "========================================"
+
+          echo ""
+          echo "--- RUNNER INFORMATION ---"
+          echo "Runner name: ${{ runner.name }}"
+          echo "Runner OS: ${{ runner.os }}"
+          echo "Runner architecture: ${{ runner.arch }}"
+
+          echo ""
+          echo "--- OPERATING SYSTEM DETAILS ---"
+          cat /etc/os-release
+
+          echo ""
+          echo "--- HARDWARE SPECIFICATIONS ---"
+          echo "CPU Model: $(lscpu | grep 'Model name' | cut -d':' -f2 | xargs)"
+          echo "CPU Cores: $(nproc)"
+          echo "CPU Architecture: $(uname -m)"
+          echo "Total Memory: $(free -h | grep 'Mem:' | awk '{print $2}')"
+          echo "Available Memory: $(free -h | grep 'Mem:' | awk '{print $7}')"
+          echo "Disk Size: $(df -h / | tail -1 | awk '{print $2}')"
+          echo "Disk Usage: $(df -h / | tail -1 | awk '{print $5}')"
+
+          echo ""
+          echo "========================================"

labs/submission1.md

@@ -0,0 +1,13 @@
+# Lab 1 Submission
+## Task 1 SSH Commit Signature Verification:
+The signature of commits provides a cryptographic guarantee of authorship and code integrity, preventing forgery of commits and protecting against the introduction of malicious changes on someone else's behalf. In DevOps practices, this is critically important, since CI/CD systems trust only verified commits for automatic builds and deployments, which creates an additional level of security in the software supply chain. Signed commits also ensure compliance with security standards, provide an auditable trace of changes, and are displayed on platforms like GitHub with the "Verified" label, increasing trust in the code in team and open-source development.
+#### Screenshots for Task 1:  
+![Verified Commit](screenshot/img1.png)
+
+PR templates standardize the code review process, forcing developers to describe changes in a structured manner. All PRS receive the same sections ("Purpose", "Changes", "Testing"), which saves reviewers time — they do not need to search for information in chaotic descriptions. Checklists automatically remind you of important actions.: tests, documentation, code style. In distributed teams, templates compensate for the lack of personal communication — a reviewer in a different time zone receives all the necessary information without additional questions.
+## Task 2 PR Template & Checklist:
+PR templates standardize the code review process, forcing developers to describe changes in a structured manner. All PR receive the same sections ("Purpose", "Changes", "Testing"), which saves reviewers time — they do not need to search for information in chaotic descriptions. Checklists automatically remind you of important actions.: tests, documentation, code style. In distributed teams, templates compensate for the lack of personal communication — a reviewer in a different time zone receives all the necessary information without additional questions.
+
+Challenges emerged during setup. I have some problem, while do Signing keys.
+#### Screenshots for Task 2:
+![PR template auto-filling the description.](screenshot/img2.png)