From 78fbf160d5af104c9d183db1fa505d186dd907e9 Mon Sep 17 00:00:00 2001 From: krasand Date: Fri, 6 Feb 2026 14:25:54 +0300 Subject: [PATCH 1/3] docs: add lab1 submission skeleton --- labs/submission1.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 labs/submission1.md diff --git a/labs/submission1.md b/labs/submission1.md new file mode 100644 index 00000000..59301646 --- /dev/null +++ b/labs/submission1.md @@ -0,0 +1,18 @@ +# Lab 1 — Submission + +## Task 1 — SSH Commit Signing + +### Why signed commits are important + + +### Proof of SSH signing + + +--- + +## Task 2 — Pull Request Template + +### PR template description + + +### Proof of PR template usage From b0ad4bcddf73ab98676340501619b07b2f3a3458 Mon Sep 17 00:00:00 2001 From: krasand Date: Fri, 6 Feb 2026 14:29:34 +0300 Subject: [PATCH 2/3] docs: explain importance of signed commits --- labs/submission1.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/labs/submission1.md b/labs/submission1.md index 59301646..86e43376 100644 --- a/labs/submission1.md +++ b/labs/submission1.md @@ -4,6 +4,10 @@ ### Why signed commits are important +Signed commits help verify that changes were made by a trusted author +and that the commit history was not altered. This is important in +DevOps workflows because it increases security, accountability, +and trust in collaborative environments. ### Proof of SSH signing From 3ad4db242a3f94afe5ecbacd56d7da4816000f0e Mon Sep 17 00:00:00 2001 From: krasand <101513792+krasand@users.noreply.github.com> Date: Fri, 6 Feb 2026 15:57:48 +0300 Subject: [PATCH 3/3] docs: complete lab1 submission --- labs/submission1.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/labs/submission1.md b/labs/submission1.md index 86e43376..960e51b0 100644 --- a/labs/submission1.md +++ b/labs/submission1.md @@ -11,6 +11,9 @@ and trust in collaborative environments. ### Proof of SSH signing +The commit "docs: explain importance of signed commits" was created +using SSH commit signing. On GitHub, this commit is marked with +a green "Verified" badge, confirming the authenticity of the author. --- @@ -18,5 +21,13 @@ and trust in collaborative environments. ### PR template description +A pull request template was added to the main branch of the repository. +It includes sections for Goal, Changes, and Testing, as well as a +checklist to ensure clear PR titles, updated documentation, and +absence of sensitive data. ### Proof of PR template usage + +A pull request from `feature/lab1` to `main` was created in my fork. +The PR description was automatically populated using the pull request template. +The checklist items were completed, demonstrating standardized PR workflow.