Add pre-commit config for repo hygiene and secret detection - #119
Add pre-commit config for repo hygiene and secret detection#119Harshaada wants to merge 1 commit into
Conversation
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe pull request adds pre-commit secret scanning with private-key detection and Gitleaks. The README documents installation, hook checks, GitHub Secret Scanning, and Push Protection. ChangesSecret scanning setup
Estimated code review effort: 1 (Trivial) | ~5 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@README.md`:
- Line 37: Update the environment configuration link in the README to reference
the heading’s exact rendered anchor, or add a stable explicit anchor and
reference it, so markdownlint-cli2 validates the fragment.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: a911cf3c-6f01-4822-95ed-dcb9fdd93f7e
📒 Files selected for processing (2)
.pre-commit-config.yamlREADME.md
| cp env.template .env | ||
| ``` | ||
|
|
||
| Edit `.env` and configure the required variables (see [Environment Configuration](#environment-configuration) below). |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Fix the invalid environment link fragment.
Line 37 uses #environment-configuration, but markdownlint-cli2 reports this fragment as invalid for the target heading. Use the exact rendered anchor or add a stable explicit anchor.
The markdownlint-cli2 result identifies this fragment as invalid.
🧰 Tools
🪛 markdownlint-cli2 (0.23.2)
[warning] 37-37: Link fragments should be valid
(MD051, link-fragments)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@README.md` at line 37, Update the environment configuration link in the
README to reference the heading’s exact rendered anchor, or add a stable
explicit anchor and reference it, so markdownlint-cli2 validates the fragment.
Source: Linters/SAST tools
No description provided.