Skip to content

spec: add RECOMMENDED label normalization #164

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
0xheartcode wants to merge 1 commit into
base: main
Choose a base branch
from
Open

spec: add RECOMMENDED label normalization #164

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 6 additions & 2 deletions ISSUE-FORMAT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -327,7 +327,10 @@ Labels: label1, label2, label3

When comparing labels for merge operations (Section 6.3), implementations
MUST trim whitespace and compare the resulting strings exactly
(case-sensitive).
(case-sensitive). Implementations SHOULD normalize labels to lowercase
before comparison to avoid case-variant duplicates (e.g., `bug` and `Bug`
being treated as distinct labels). This normalization is RECOMMENDED but
not REQUIRED, to preserve intentional casing (e.g., `iOS`, `API`, `UI`).

### 4.8 Formal Grammar (ABNF)

Expand Down Expand Up @@ -549,7 +552,8 @@ known limitations:
**1. Case Variants**:
- `bug` and `Bug` are distinct labels
- Concurrent addition of both creates duplicates: `bug, Bug`
- Resolution: Manual cleanup or project conventions
- Resolution: Implementations SHOULD apply lowercase normalization per
Section 4.7. Projects SHOULD establish consistent casing conventions.

**2. Semantic Duplicates**:
- `enhancement` and `feature` are distinct labels
Expand Down