Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
31 commits
Select commit Hold shift + click to select a range
c62ec90
feat: add lab1 task 1 submission
arinapetukhova Jan 30, 2026
c112fbe
feat: summary of signing commits benefits
arinapetukhova Jan 30, 2026
0f2867f
verified commit
arinapetukhova Jan 30, 2026
b9a96c1
verified commit
arinapetukhova Jan 30, 2026
3cb6e7e
verified commit
arinapetukhova Jan 30, 2026
71b5840
feat: SSH screenshots added
arinapetukhova Jan 30, 2026
63466e5
feat: SSH screenshots added
arinapetukhova Jan 30, 2026
d6b77e7
feat: SSH screenshots added
arinapetukhova Jan 30, 2026
e7d91e0
remove screenshots folder
arinapetukhova Jan 30, 2026
3c838d9
remove .DS_Store file
arinapetukhova Jan 30, 2026
6b3604a
feat: SSH screenshots added
arinapetukhova Jan 30, 2026
fcfd20b
feat: task 2 added
arinapetukhova Jan 30, 2026
74c38e3
Add test file
arinapetukhova Feb 6, 2026
5a2f7d3
lab 2, task 1
arinapetukhova Feb 6, 2026
bcf2426
task 1
arinapetukhova Feb 6, 2026
736f6df
task 2
arinapetukhova Feb 7, 2026
dca8922
task 3 & 4
arinapetukhova Feb 7, 2026
aedb432
new tag
arinapetukhova Feb 7, 2026
137cbae
task 3 & 4
arinapetukhova Feb 7, 2026
d87efa4
task 5 & 6
arinapetukhova Feb 7, 2026
74d9f80
GitHub Actions workflow testing
arinapetukhova Feb 13, 2026
e715193
lab 3 task 1
arinapetukhova Feb 13, 2026
c495280
manual workflow
arinapetukhova Feb 13, 2026
320bb75
manual workflow
arinapetukhova Feb 13, 2026
9f373bb
task 2
arinapetukhova Feb 13, 2026
ec5f3fc
task 2
arinapetukhova Feb 13, 2026
9b8f23f
lab 4, tasks 1 & 2
arinapetukhova Feb 21, 2026
746ce31
lab5 tasks 1 & 2
arinapetukhova Feb 27, 2026
cd40892
format fixed
arinapetukhova Feb 27, 2026
30c4637
format fixed
arinapetukhova Feb 27, 2026
5fed085
Update submission5.md
arinapetukhova Feb 27, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
52 changes: 52 additions & 0 deletions .github/workflows/github-actions-demo.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,52 @@
name: GitHub Actions Demo
run-name: ${{ github.actor }} is testing out GitHub Actions 🚀
on:
push:
workflow_dispatch:

jobs:
Explore-GitHub-Actions:
runs-on: ubuntu-latest
steps:
- run: echo "🎉 The job was automatically triggered by a ${{ github.event_name }} event."
- run: echo "🐧 This job is now running on a ${{ runner.os }} server hosted by GitHub!"
- run: echo "🔎 The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}."

- name: Check out repository code
uses: actions/checkout@v5

- run: echo "💡 The ${{ github.repository }} repository has been cloned to the runner."
- run: echo "🖥️ The workflow is now ready to test your code on the runner."

- name: List files in the repository
run: |
ls ${{ github.workspace }}

- name: Gather system information
run: |
echo "## System Information"
echo "### Operating System Details"
cat /etc/os-release
echo ""
echo "### CPU Information"
lscpu | grep "Model name\|CPU(s)"
echo ""
echo "### Memory Information"
free -h
echo ""
echo "### Disk Information"
df -h
echo ""
echo "### Kernel Version"
uname -a
echo ""
echo "### Who am I"
whoami
echo ""
echo "### Current Directory"
pwd
echo ""
echo "### Environment Variables"
env | sort

- run: echo "🍏 This job's status is ${{ job.status }}."
Binary file added labs/screenshots/.DS_Store
Binary file not shown.
Binary file added labs/screenshots/img1.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added labs/screenshots/img2.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added labs/screenshots/img3.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added labs/screenshots/img4.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added labs/screenshots/img5.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added labs/screenshots/img6.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added labs/screenshots/img7.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
25 changes: 25 additions & 0 deletions labs/submission1.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
# Lab 1 Submission
## Task 1: SSH Commit Signature Verification

Commit signing proves who made code changes and that they weren't altered. It uses special digital signatures to confirm that a developer really created those commits and nobody secretly changed them. This stops people from pretending to be other team members, creates trust in team projects, and makes automated software pipelines safer.

In DevOps workflows, where code moves quickly from writing to deployment, signed commits are important because they keep track of who did what and make sure only trusted changes get deployed.

#### Screenshots for Task 1:
![SSH Key on GitHub](screenshots/img1.png)
![Verified Commit](screenshots/img3.png)
![Terminal Logs](screenshots/img2.png)

## Task 2: PR Template & Checklist

PR templates make team collaboration smoother and more efficient. By providing a standard structure for every pull request, they ensure that all necessary information is included from the start. When everyone uses the same format with sections like Goal, Changes, and Testing, reviewers know exactly where to look for information instead of going through comments or asking repetitive questions. The checklist also prevents common mistakes, like forgetting to update documentation or accidentally including sensitive files.

Templates saves time and reduces frustration for everyone. New team members can quickly understand what's expected, experienced developers don't waste time on incomplete submissions, and the entire review process becomes more predictable. In fast-paced DevOps workflows where code moves quickly through automated pipelines, these templates create a reliable foundation that helps teams maintain quality while moving fast together.

Several challenges emerged during setup. I initially found the repository structure confusing: understanding that work flows from the course repo to my fork to a feature branch. SSH key setup also required troubleshooting: I had to re-add my key as a "Signing Key" instead of just for authentication. Finally, I learned PR templates must exist on the main branch before they auto-fill, and they serve as empty forms that users complete when opening each PR.

#### Screenshots for Task 2:
![Template Existance in Terminal](screenshots/img4.png)
![Template Existance on GitHub](screenshots/img5.png)
![PR template auto-filling the description](screenshots/img6.png)
![PR template filled](screenshots/img7.png)
Loading