Repository navigation
docs: add SECURITY.md and document the main-protection ruleset - #42
Merged
Merged
Conversation
main now has the repo ruleset "main protection" (id 26118885). It is PR-only, requires the Build & Test check and has no bypass. README.md and DEPLOY.md said to deploy with `git push` to main, which the ruleset now rejects; they now say to merge a PR. AGENTS.md gains a gotcha: renaming the Build & Test job must update the ruleset in the same PR. SECURITY.md points reporters to GitHub's private advisory form, which is now on, and to security.txt for email. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Summary
SECURITY.md. It points reporters to GitHub's private advisory form, which is now switched on, and to the site'ssecurity.txtfor email.26118885). It is PR-only, requiresBuild & Testand has no bypass.README.mdandDEPLOY.mdsaid to deploy withgit pushtomain, which the ruleset now rejects. They now say to merge a PR.DEPLOY.mdkeeps the first-push step for a brand-new repo.AGENTS.mdhas a new gotcha: renaming theBuild & Testjob must update the ruleset in the same PR, or every PR blocks.CHANGELOG.mdhas entries for both.This is the first PR under the ruleset, so it also tests that a PR can merge.
Deploy impact
Merging redeploys the site with no content change.
*.mdfiles are excluded from the S3 sync. The HTML pages are re-uploaded with a new?v=cache-bust, and CloudFront is invalidated.Test plan
Build & Testpasses on this PRmergeStateStatusisCLEANbefore merging, which proves the required-check name matchesCIrun onmain(the deploy) succeeds after the merge🤖 Generated with Claude Code