Contributing guidelines for branch prefixes #780
+15
−0
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
Contributor
Author
|
Feel free to discuss or suggest changes! |
Member
|
Suggestion: Include a prefix for scripts, e.g. "scripts". |
Contributor
Author
Do we disambiguate between features, fixes, and refactors for scripts? e.g. do we use |
Collaborator
Maybe since scripts is a small coverage area we could just use scripts/description. It'll likely only be targeting one script to update at a time. |
…into docs/branch_prefix_guidelines
Contributor
Author
|
Added |
AnnaKwa
approved these changes
Feb 10, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
This PR updates the contributing guidelines with internal development guidelines for branch names.