Repository navigation
docs: state the repository file rules in AGENTS.md - #52
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.
Adds three rules to the
Naming and documentationsection, betweenrepository-filesmarkers so the block is a single copy that can be checked and replaced.They exist because the file set a repository owes its readers depends on whether it is public, and an agent asked to write a
SECURITY.mdwill otherwise invent a shape — different every time, and sometimes the wrong one of the two.The three are: which files each kind of repository needs, that a public security policy describes disclosure while a private one describes credential rotation, and that GitHub template filenames use underscores.
The content-boundary block in the
Do notsection is unchanged.