github-qa-labels

Source excerpt starting at line 1.

1---2name: github-qa-labels3description: Label GitHub issues and PRs found during QA testing. Use when organizing QA findings with proper labels.4allowed-tools: Bash5---6 7# GitHub QA Labels8 9When creating or organizing issues/PRs found during QA testing, apply these labels.10 11## QA tracking label12 13Add `upgrade:<version>` label to track all QA findings for a release:14 15```bash16# Create label if it doesn't exist17gh label create "upgrade:10.2" --repo storybookjs/storybook --color "0E8A16" --description "Issues/PRs found during 10.2 upgrade QA"18 19# Add to issue/PR20gh issue edit <NUMBER> --repo storybookjs/storybook --add-label "upgrade:10.2"21gh pr edit <NUMBER> --repo storybookjs/storybook --add-label "upgrade:10.2"22```23 24## Severity labels25 26Add `sev:S1` through `sev:S4` to **bugs only** (not docs or feature requests):27 28```bash29gh issue edit <NUMBER> --repo storybookjs/storybook --add-label "sev:S2"30```31 32Severity levels:33 34- **sev:S1**: Critical, blocking, no workaround35- **sev:S2**: Significant issue, may have workaround36- **sev:S3**: Moderate issue, workaround exists37- **sev:S4**: Minor issue, edge case, easy workaround38 39## What gets severity labels40 41| Type                    | Severity label? |42| ----------------------- | --------------- |43| Bug (runtime error)     | Yes             |44| Bug (type error)        | Yes             |45| Bug (automigrate issue) | Yes             |46| Documentation issue     | No              |47| Feature request         | No              |48| Enhancement             | No              |49 50## Batch labeling51 52Label multiple issues at once:53 54```bash55gh issue edit 33524 --repo storybookjs/storybook --add-label "upgrade:10.2" && \56gh issue edit 33527 --repo storybookjs/storybook --add-label "upgrade:10.2" && \57gh pr edit 33526 --repo storybookjs/storybook --add-label "upgrade:10.2"58```59