Feature/lab3 - #3
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Goal
Implement SSH commit signing with GitHub verification and add automated secret detection using pre-commit and gitleaks.
Changes
Added
.pre-commit-config.yamlgitleaks(v8.26.0)detect-private-keycheck-added-large-filesAdded
submissions/lab3.mdgit filter-repohistory rewrite exerciseTesting
git log --show-signature -1 pre-commit install pre-commit run --all-files git commit -m "test: should be blocked by gitleaks"Observed results:
The fake GitHub Personal Access Token was successfully detected and the commit was blocked by gitleaks.
Artifacts & Screenshots
submissions/lab3.mdVerified Commit
Paste the screenshot showing the green Verified badge below:

Checklist
feat(lab3): <topic>stylesubmissions/lab3.md