Skip to content

Add release notes configuration and PR label guidelines #77

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

Merged
lollipop-onl merged 2 commits into from
Mar 10, 2026
Merged

Add release notes configuration and PR label guidelines #77

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a7caaf7
Add release notes configuration and PR label guidelines
lollipop-onl Mar 10, 2026
bcb22b2
Clarify enhancement label scope in PR labeling guidelines
lollipop-onl Mar 10, 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
29 changes: 29 additions & 0 deletions .github/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
changelog:
exclude:
labels:
- duplicate
- invalid
- wontfix
- question
categories:
- title: Breaking Changes
labels:
- breaking
- title: New Features
labels:
- enhancement
- title: Bug Fixes
labels:
- bug
- title: Performance
labels:
- performance
- title: Documentation
labels:
- documentation
- title: Dependencies
labels:
- dependencies
- title: Other Changes
labels:
- "*"
17 changes: 17 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -459,3 +459,20 @@ Plan files (implementation plans, design docs, etc.) go in `.claude/plans/`.
- **PR / Issue titles**: Always in English.
- **PR / Issue body**: English by default unless otherwise specified.
- **PR assignee**: Always use `--assignee @me` to assign the PR to the current user.

### PR Labels

PRs must have at least one label for release note categorization (`.github/release.yml`). Apply the most specific label:

| Label | When to use |
| --------------- | ---------------------------------------------------- |
| `breaking` | Breaking changes (removal, rename, behavioral shift) |
| `enhancement` | New features |
| `bug` | Bug fixes |
| `performance` | Performance improvements |
| `documentation` | Documentation-only changes |
| `dependencies` | Dependency updates (auto-applied by dependabot) |

Use `enhancement` only for end-user-facing features — changes that a `bee` CLI user would notice. CI configuration, repo maintenance, developer experience improvements, and internal refactors do not qualify and should be left unlabeled (they appear under "Other Changes").

PRs without these labels appear under "Other Changes" in release notes.