docs: define pull request label usage - #326
Merged
Merged
Conversation
4 tasks
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.
Change
Document a small PR label scheme using the existing change-type and product labels. Keep
perf:fullas an independent performance-verification trigger, and point contributors to the rule from the contribution guide and PR template.The currently open PRs were classified and labeled separately on GitHub. Storage-write PR #319 and the better-sqlite3 update PR #146 also received
perf:fullunder the existing performance rules.Validation
git diff --check origin/main...HEAD: passed.pnpm verify --profile docs: passed all 4 applicable gates on macOS; release-tool tests had 51 passes and 1 platform-specific skip.Publication and contribution checks
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.