Change Feature request template's label from documentation to enhancement
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 90/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- github
- Domain
- tooling
Research direction
Open .github/ISSUE_TEMPLATE/feature_request.md and inspect the YAML front matter, especially the labels: key between title: and assignees:. Confirm that only the feature request label changes, then after the PR merges to main, use the issue template chooser to verify the draft shows enhancement rather than documentation and close the draft without submitting.
Written by the indexing model from the issue text.
Description
Overview
We need to change the label applied by the "Feature request" issue template from documentation to enhancement, because every feature suggestion opened through it is currently filed as documentation work. This makes the documentation label useless as a filter and hides real feature requests from anyone browsing by enhancement.
Action Items
- In
.github/ISSUE_TEMPLATE/feature_request.md, change the front matter linelabels: documentation(line 5 at time of writing) tolabels: enhancement. If the line number has drifted, it is thelabels:key in the YAML front matter at the top of the file, betweentitle:andassignees:. - After the PR merges to
main, verify: open https://github.com/hackforla/incubator/issues/new/choose, start a "Feature request", and confirm the right-hand Labels box showsenhancementand notdocumentation. Close the draft without submitting. This step cannot be done from the PR branch — GitHub serves issue templates from the default branch only, so the change is invisible until it merges. Don't close this issue until you have checked. - Leave the rest of the template alone — only the label is in scope.
Resources/Instructions
- File to edit: https://github.com/hackforla/incubator/blob/main/.github/ISSUE_TEMPLATE/feature_request.md
- Both
documentationandenhancementalready exist as labels in this repo, so no label needs creating: https://github.com/hackforla/incubator/labels - This template is one of the ones being kept, not one of the 15 slated for deletion in #146 — so it is worth fixing rather than removing.
- Dominant language
- HCL
- Stars
- 6
- Forks
- 18
- Avg merge
- 1h 6m
- Merged PRs (30d)
- 44
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hackforla/incubator
-
complexity: small feature: templates good first issue role: DevOps Engineer size: 1pt
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
complexity: small feature: project terraform setup good first issue role: DevOps Engineer size: 1pt
Difficulty 3/5 1-2 days Newbie friendliness 76/100
-
complexity: medium feature: Onboarding role: DevOps Engineer size: 5pt
Difficulty 5/5 Over a week Newbie friendliness 42/100
-
Bump dflook/terraform-plan and terraform-apply from v1 to v3 in incubator's Terraform workflows Opencomplexity: small feature: GHA role: DevOps Engineer size: 1pt
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
complexity: medium feature: GHA role: DevOps Engineer size: 2pt
Difficulty 3/5 1-2 days Newbie friendliness 68/100
All issues in hackforla/incubator
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hemilabs/ui-monorepo#2332 ·
-
Help-Wanted Needs-Triage Package-Update
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/winget-pkgs#438662 ·
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
olcf/olcf-test-harness#278 · 1 comment ·