Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Feature/lab1 #1470
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
Feature/lab1 #1470
Changes from all commits
cdedef3cfb3cd60f00d0b0415f0c422a775ec8ac6d45eeb62f0972d8563789e503626d3767935c5683aaFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Lab 1 submission
curl.exe -s http://localhost:8080/health
{"notes":4,"status":"ok"}
curl.exe -s http://localhost:8080/notes
[{"id":1,"title":"Welcome to QuickNotes","body":"This is the project you'll containerize, deploy, monitor, and harden across all 10 labs.","created_at":"2026-01-15T10:00:00Z"},{"id":2,"title":"Read app/main.go first","body":"Start by understanding the entry point — env vars, signal handling, graceful shutdown.","created_at":"2026-01-15T10:05:00Z"},{"id":3,"title":"DevOps mantra","body":"If it hurts, do it more often.","created_at":"2026-01-15T10:10:00Z"},{"id":4,"title":"Endpoint cheat-sheet","body":"GET /notes GET /notes/{id} POST /notes DELETE /notes/{id} GET /health GET /metrics","created_at":"2026-01-15T10:15:00Z"}]
$ curl -s -X POST http://localhost:8080/notes -H 'Content-Type: application/json' -d '{"title":"Lab1","body":"Test note"}'
{"id":5,"title":"Lab1","body":"Test note","created_at":"2026-07-24T20:13:34.6665007Z"}
git log --show-signature -1
commit cdedef37dd8b112e8a4c7aaf1041ca2b6628ffd8 (HEAD -> feature/lab1, origin/feature/lab1) Good "git" signature with ED25519 key SHA256:vuvpBEsEe4gFA2Rw0DBfxr1CyFc1Q3jyEq2vWO65JAI Author: AlisaEvdosenko evdosenko.dds@gmail.com Date: Fri Jul 24 23:02:20 2026 +0300
docs(lab1): start submission
Signed-off-by: AlisaEvdosenko evdosenko.dds@gmail.com
Signed commits are crucial for supply chain security. The xz-utils backdoor incident in March 2024 demonstrated how a compromised maintainer account could have introduced malicious code. Signed commits help verify that code actually comes from the claimed author, not an impersonator. This adds a layer of trust in open-source ecosystems and prevents supply chain attacks where bad actors could inject malicious code through compromised accounts.
Why Signed Commits Matter
Signed commits are crucial for supply chain security. The xz-utils backdoor incident in March 2024 demonstrated how a compromised maintainer account could have introduced malicious code. Signed commits help verify that code actually comes from the claimed author, not an impersonator. This adds a layer of trust in open-source ecosystems and prevents supply chain attacks where bad actors could inject malicious code through compromised accounts.
GitHub Community
Why Starring Repositories Matters in Open Source
Starring repositories on GitHub is a simple but powerful way to show appreciation for open-source projects. It helps developers gain visibility for their work, increases project discoverability, and serves as a social signal to the community that a project is useful and worth exploring. For maintainers, stars provide motivation and validation that their work is valued.
How Following Developers Helps in Team Projects and Professional Growth
Following other developers on GitHub allows you to stay updated on their contributions, learn from their coding practices, and discover new tools and libraries. In team projects, it helps you understand your colleagues' expertise and areas of interest. Professionally, it builds your network, exposes you to different approaches to solving problems, and can lead to mentorship opportunities and career growth.
PS C:\Users\user\DevOps-Intro> git commit --no-gpg-sign -s --allow-empty -m "test: unsigned commit (should fail)" [main 3226893] test: unsigned commit (should fail) PS C:\Users\user\DevOps-Intro> git push origin main Enter passphrase for key '/c/Users/user/.ssh/id_ed25519': Enumerating objects: 1, done. Counting objects: 100% (1/1), done. Writing objects: 100% (1/1), 225 bytes | 75.00 KiB/s, done. Total 1 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0) remote: error: GH013: Repository rule violations found for refs/heads/main. remote: Review all repository rules at https://github.com/AlisaRyba/DevOps-Intro/rules?ref=refs%2Fheads%2Fmain remote: remote: - Changes must be made through a pull request. remote: remote: - Commits must have verified signatures. remote: Found 1 violation: remote: remote: 32268937d5dcd95d3b0b355878ae65ca1477396c remote: To github.com:AlisaRyba/DevOps-Intro.git ! [remote rejected] main -> main (push declined due to repository rule violations) error: failed to push some refs to 'github.com:AlisaRyba/DevOps-Intro.git'
If Knight Capital had enforced branch protection and required signed commits on their production deployment branch, the catastrophic deploy day in 2012 might have been prevented. The protection rules would have required a pull request with at least one approving review before any changes could be merged to the production branch, ensuring that the deployment process was not triggered by a single person's manual action. Additionally, requiring signed commits would have verified the identity of the engineer who submitted the changes, making it easier to audit the deployment history and hold the right individuals accountable. While this wouldn't have caught the logical error in the code itself, it would have added critical human oversight and a formal audit trail, significantly reducing the risk of such an uncontrolled deployment.