Verify signing test

.github/pull_request_template.md

@@ -0,0 +1,17 @@
+# Pull Request Template
+
+## Goal
+Describe the purpose of this PR and what it aims to achieve.
+
+## Changes
+- Summarize the main changes made in this PR.
+- Highlight any new features, fixes, or refactors.
+
+## Testing
+- Explain how these changes were tested.
+- Include steps for manual verification or automated tests.
+
+## Checklist
+- [x] PR has a clear, descriptive title
+- [x] Documentation / README updated if needed
+- [x] No secrets or large temporary files included

labs/lab1.md

@@ -1,4 +1,4 @@
-# Lab 1 — Introduction to DevOps & Git Workflow
+git config --global gpg.format ssh# Lab 1 — Introduction to DevOps & Git Workflow
 
 ![difficulty](https://img.shields.io/badge/difficulty-beginner-success)
 ![topic](https://img.shields.io/badge/topic-DevOps%20Basics-blue)

submission1.md

@@ -0,0 +1,12 @@
+# Benefits of Signing Commits
+
+Signed commits provide cryptographic proof of authorship. This ensures that the commit truly comes from the claimed developer and has not been modified afterward. The main benefits are:
+
+- **Authenticity**: Verifies that commits were created by a trusted source.  
+- **Integrity**: Detects if commit history was altered or tampered with.  
+- **Accountability**: Ties commits directly to an individual’s verified identity.  
+- **Security in Collaboration**: Protects against malicious actors pushing unverified or fake commits in shared repositories.  
+- **Compliance**: Some organizations require signed commits for audit and regulatory purposes.  
+
+SSH commit signature verification strengthens security by using secure keys already managed for repository access, reducing reliance on weaker authentication methods.
+Also, helpful in deployment: when you work in terminal of server with private repository.