[Docs] CONTRIBUTING_GUIDELINES prescribes branch names and labels the repo does not use #642

Closed
opened 2026-07-22 16:23:39 +00:00 by brenno · 1 comment
Owner

Found in the pre-publication contributor-journey review.

Evidence: docs/CONTRIBUTING_GUIDELINES.md:116-117 prescribes feature/short-description and bugfix/issue-number-…. Across the last 200 merges on main: fix/ 64, feat/ 59, docs/ 28, refactor/ 12, land/ 11, test/ 8, chore/ 3, sec/ 2, ci/ 1 — and zero feature/ or bugfix/.

Lines 126-130 of the same file list the tracker categories as Bug, Enhancement, Feature, Documentation, Security; the live label set has no Feature and no Documentation (it is docs), and omits privacy, triage, accepted, declined, needs-info and duplicate.

Why this matters: these are the two most mechanical instructions in the document, and both are wrong against the repository own visible history — the first thing a contributor can check, and the cheapest possible way to teach them that the rest of the document is decorative.

Proposal: replace the two branch prefixes with the six the repository actually uses, and replace the invented category list with the real labels (pull them from the API once and paste). Two edits, one file. Good first issue.

Found in the pre-publication contributor-journey review. **Evidence:** `docs/CONTRIBUTING_GUIDELINES.md:116-117` prescribes `feature/short-description` and `bugfix/issue-number-…`. Across the last 200 merges on `main`: `fix/` 64, `feat/` 59, `docs/` 28, `refactor/` 12, `land/` 11, `test/` 8, `chore/` 3, `sec/` 2, `ci/` 1 — and **zero** `feature/` or `bugfix/`. Lines 126-130 of the same file list the tracker categories as *Bug, Enhancement, Feature, Documentation, Security*; the live label set has no `Feature` and no `Documentation` (it is `docs`), and omits `privacy`, `triage`, `accepted`, `declined`, `needs-info` and `duplicate`. **Why this matters:** these are the two most mechanical instructions in the document, and both are wrong against the repository own visible history — the first thing a contributor can check, and the cheapest possible way to teach them that the rest of the document is decorative. **Proposal:** replace the two branch prefixes with the six the repository actually uses, and replace the invented category list with the real labels (pull them from the API once and paste). Two edits, one file. Good first issue.
Author
Owner

Opgelost in `cc00070` (PR #655).

De acht takprefixen die deze repo werkelijk gebruikt staan er nu, met hun aantallen over de laatste 200 merges (fix/ 63, feat/ 48, docs/ 21, land/ 11, test/ 8, refactor/ 8, chore/ 3, sec/ 2). De labellijst is vervangen door de echte set van de tracker, inclusief privacy en de triagelabels die ontbraken.

Opgelost in \`cc00070\` (PR #655). De acht takprefixen die deze repo werkelijk gebruikt staan er nu, met hun aantallen over de laatste 200 merges (`fix/` 63, `feat/` 48, `docs/` 21, `land/` 11, `test/` 8, `refactor/` 8, `chore/` 3, `sec/` 2). De labellijst is vervangen door de echte set van de tracker, inclusief `privacy` en de triagelabels die ontbraken.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
LibreKAT/Ocideck#642
No description provided.