Clean up labels
See original GitHub issueI want to clean up some of our labels
Full list
good first issue
Status - in progress
Action - awaiting feed-back
Action - needs grooming
Prio 1 - must have
Prio 2 - should have
Prio 3 - could have
Prio 4 - won’t have
Size 0 - Briefing
Size 1 - small
Size 2 - medium
Size 3 - large
Size 4 - too big
Status - duplicate
Status - workable
Status - up Next
hackathon
beta-release
help wanted
question
wontfix
invalid
duplicate
enhancement
bug
Work in progress
documentation
do not merge
pending PR
hacktoberfest
needs-plugin-issue
feature
fix
chore
test
pinned
plugin-compatibility
stale
reverted
Here’s what I suggest
Remove
label : reason
Status - in progress : unused
Action - awaiting feed-back : unused
Action - needs grooming : unused
Prio 1 - must have : unused
Prio 2 - should have : unused
Prio 3 - could have : unused
Prio 4 - won’t have : unused
Size 0 - Briefing : unused
Size 1 - small : unused
Size 2 - medium : unused
Size 3 - large : unused
Size 4 - too big : unused
Status - duplicate : unused
Status - workable : unused
Status - up Next : unused
beta-release : unused
Work in progress : replaced by WIP[bot]
do not merge : replaced by WIP[bot]
pending PR : debatable just as easily marked by WIP or 🚧
needs-plugin-issue - replaced by plugin-compatibility
invalid : replaced by stale[bot]
Stay
label : reason
good first issue : used by github for finding new contributors
help wanted : used by github for finding new contributors
hackathon : useful for hackathon events
question : signal value
wontfix : useful to find things we wontfix
duplicate : signal value
enhancement : enhancement we want to get to (exempted from stale[bot])
bug : signal value
documentation : release drafter
hacktoberfest : event
feature : release drafter
fix : release drafter
chore : release drafter
test : release drafter
pinned : exempted from stale[bot]
plugin-compatibility : used by issue template
stale : stale[bot]
reverted : release drafter
Some that require extra explanation.
invalid
would be the same as stale since stale[bot] will clean up if a user doesn’t reply within 7 days if we mark it stale.
Work in progress
/do not merge
add WIP or 🚧 to PR title.
I will update the PR template to make this clear.
I suggest we use 🚧 as a convention as we do like emojis :trollface:
Perhaps we should replace enhancement
with feature
to avoid confusion
(I prefer the word feature over enhancement)
I would like to use probot/settings to achieve this cleanup 😅
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Clean up list of labels in Jira Software - Atlassian Community
Solved: Hi guys! How do I clean up my list of labels in Jira i.e I want to remove it from my project...
Read more >The Complete Guide to Label Removal - Instructables
1. Label/sticker removal from new purchases is both the first and foremost application and the most straightforward. After all, when you buy something...
Read more >6 Ways to Remove Product Stickers & Labels - Avery
Get your containers clean & ready for new products with simple label removal tips · 1. Nail polish remover or rubbing alcohol ·...
Read more >23 Best label removing ideas | household hacks, diy cleaning ...
Jan 28, 2017 - Explore Pam McKee's board "label removing", followed by 502 people on Pinterest. See more ideas about household hacks, diy...
Read more >Cleaning Labels - Accuform
Most people will agree that a clean workplace is an efficient workplace - that's why you need Cleaning Labels in your business.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
No that is because of templates 😆 See https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/.github/ISSUE_TEMPLATE/2-feature-request.md
yeah makes sense