Repository navigation
Set standards for branches, commits, pull requests and releases - #29
Merged
Merged
Conversation
CONTRIBUTING.md now covers branches and commits, and says every change reaches main through a pull request, the maintainer's included, once a build with it has been tested. MAINTAINING.md covers review, merging, labels, releases and the repository rules. New pull request and issue templates ask for what those standards need. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
SumirSeth
added
documentation
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.
What changed
CONTRIBUTING.mdnow has sections on branches and commits. It says every change reachesmainthrough a pull request, the maintainer's included, once CI passes and a build with the change has been tested (any build, not necessarily Nightly). Mentions of Discussions are gone.MAINTAINING.mdcovers reviewing, merging (rebase only), issues and labels, the release steps, semver while on 0.x, and the repository rulesets..github/pull_request_template.mdasks for: what, why, how it was verified (build and setup), performance, what wasn't tested,Fixes #, plus a short checklist.performance,windows-10andneeds-repro.Why
These put the repository standards we agreed on in writing, so contributors and the maintainer follow the same rules, and the templates prompt for them.
How I verified it
Docs and templates only. I checked the relative links and the YAML structure of the issue forms. GitHub only shows the forms once this is merged to the default branch.
Performance
Not affected.
Not tested
How the issue forms render on GitHub, which is only possible after merging.
🤖 Generated with Claude Code