Skip to content

chore: add build/chore/security labels and release notes categories #73

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mwbrooks wants to merge 5 commits into
base: main
Choose a base branch
from
+18 −4
Open

chore: add build/chore/security labels and release notes categories #73

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
5b48b85
chore: add chore + security labels and align release notes categories
mwbrooks Jul 2, 2026
ea06d05
chore: move Security back to original position in release.yml
mwbrooks Jul 2, 2026
8b6f2ed
chore: rename documentation label to docs
mwbrooks Jul 2, 2026
cf285eb
chore: add Build category and build label
mwbrooks Jul 3, 2026
4878e01
docs: expand Issue Triage labels list in maintainers guide
mwbrooks Jul 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 10 additions & 2 deletions .github/maintainers_guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -110,8 +110,16 @@ Patch and minor updates are auto-approved and auto-merged via the
checking whether the relevant live `docs.slack.dev` page has changed.
- 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.

@zimeg zimeg Jul 3, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👁️‍🗨️ 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!

@mwbrooks mwbrooks Jul 3, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed, good catch @zimeg. Commit 4878e01 has updated this section to list all of our labels and how we suggest that are used.

- Labels:
- `bug` — confirmed defects
- `enhancement` — feature requests and new functionality
- `docs` — documentation-only changes
- `test` — test-only changes
- `build` — CI, GitHub Actions, and build/compilation processes
- `chore` — repo structure, required files, release scaffolding, general maintenance
- `dependencies` — dependency updates (Dependabot applies this automatically)
- `security` — vulnerability fixes, hardening, and security audit findings
(apply alongside `bug`/`build`/`dependencies` as appropriate)

---

Expand Down
10 changes: 8 additions & 2 deletions .github/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,9 +13,15 @@ changelog:
- title: 🤖 Build
labels:
- build
- title: 🧪 Testing/Code Health
- title: 🧪 Tests
labels:
- code health
- test
- title: 🧹 Chores

@mwbrooks mwbrooks Jul 2, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

note: Moved belong Tests because externally developers are impacted by this less.

labels:
- chore
- title: ⬆️ Dependencies
labels:
- dependencies
- title: 🔒 Security
labels:
- security
Comment on lines 25 to 27

@zimeg zimeg Jul 3, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔏 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?

Expand Down