Repository navigation
Require PRs for every change and block sensitive info - #2
Merged
Merged
Conversation
- scripts/check-sensitive.sh fails on non-noreply commit emails, emails in added content (GitHub/Anthropic noreply allowed), local home paths and device/simulator ids; runs in CI and as an opt-in pre-commit hook - sensitive-check workflow runs it plus gitleaks on every PR and push to main - land skill and lander now land through a pull request (push branch, open PR, wait for checks, rebase-merge); nothing pushes to the default branch - orchestration skill and README state the PR-only rule; README documents the protections and the hook Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LwG41BKPezSJuGPH9JGBuM
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.
Why
mainshould only change through reviewed PRs, and personal or machine info (emails, home paths, device IDs, secrets) should never reach this public repo.What changed
scripts/check-sensitive.shfails on:/Users/<name>,/home/<name>)sensitive-checkworkflow runs that script plus gitleaks on every PR and on pushes to main. It will be the required check for merging..githooks/pre-commitruns the same check locally (opt in withgit config core.hooksPath .githooks).landskill and lander push a branch, open a PR, wait for checks, then rebase-merge. Nothing pushes to the default branch.After merge (repo settings, applied separately)
main: PR required, thesensitive-checkstatus check required, no force-push, no deletion, no bypass (owner included).Verified
/Users/<name>path and simulator UDID in staged content, plus a commit authored with a personal email, were all flagged (exit 1). Clean content passes (exit 0).🤖 Generated with Claude Code
https://claude.ai/code/session_01LwG41BKPezSJuGPH9JGBuM