chore: add build, chore, security labels and align release notes categories#73
chore: add build, chore, security labels and align release notes categories#73mwbrooks wants to merge 4 commits into
Conversation
Introduce a `chore` label for maintainer PRs (CI, build tooling, release scaffolding, repo files) matching the conventional-commit `chore:` prefix already in use, plus a `security` label for vulnerability fixes and hardening. Rework `.github/release.yml` to match the labels that actually exist on the repo — the prior config referenced non-existent `build`, `code health`, `docs`, and `security` labels, so those changelog sections silently fell through to "Other changes". Also splits `dependencies` into its own section so Dependabot PRs don't drown out real chores.
| labels: | ||
| - docs | ||
| - title: 🤖 Build | ||
| - documentation |
There was a problem hiding this comment.
fixed: This was pointing to the wrong label name.
There was a problem hiding this comment.
📚 note: IIRC docs is matched across most projects. I'm tempted to suggest it's used here too?
There was a problem hiding this comment.
Sure, we can fix this label if we've been using docs consistently!
Restores the Security category to its prior slot near the bottom of the changelog category list.
| - build | ||
| - title: 🧪 Testing/Code Health | ||
| - test | ||
| - title: 🧹 Chores |
There was a problem hiding this comment.
note: Moved belong Tests because externally developers are impacted by this less.
| labels: | ||
| - docs | ||
| - title: 🤖 Build | ||
| - documentation |
There was a problem hiding this comment.
📚 note: IIRC docs is matched across most projects. I'm tempted to suggest it's used here too?
Match the shorter `docs` form used across other slackapi projects. The GitHub label itself was renamed in place (preserves existing PR/issue associations); this updates the `.github/release.yml` reference to match.
Match slack-cli's `build` label ("Changes to compilation and CI processes",
color #615196) for CI and build-tooling PRs. Narrows the `chore` scope to
repo files, release scaffolding, and general maintenance.
| - title: 🔒 Security | ||
| labels: | ||
| - security |
There was a problem hiding this comment.
🔏 thought(non-blocking): Following bugs or enhancements with this section might be easiest to follow in updates but I'm most excited for correct labels at this time. Let's save these reorderings for a wide spread follow up?
| - Feature requests for new skills should be discussed in the issue before | ||
| implementation begins. | ||
| - Labels: `bug` for confirmed issues, `enhancement` for feature requests, | ||
| `build` for CI/tooling changes. |
There was a problem hiding this comment.
👁️🗨️ note: I might continue to use build for some of these changes. Please do feel free to correct me in ongoing changes if something seems odd!
Summary
This pull request introduces 3 new labels (
chore,build, andsecurity) and fixes the.github/release.ymlto not use non-existent labels.chorelabel for maintainer task PRs.chore:prefix.buildlabel for changes to compilation and CI processessecuritylabel so security fixes surface distinctly in release notes..github/release.ymlwith the labels that actually exist on the repo.build,code health,docs,security), so those changelog sections silently fell through to "Other changes."documentationlabel was renamed todocsto match other slackapi projects.Preview
Testing
chorelabel, serving as the first live test of the new label + release-notes category.Notes
maintainers_guide.md).Requirements
make testand the tests pass.