The GitHub Label Cleanup Proposal #3920
Labels
status: pending triage
The bug or PR has not been reviewed yet.
type: enhancement
Provides an enhancement or new feature.
Overview
The labeling system in this repository has become more and more useful since 0.3.0 was released.
For example, the
status
andtype
labels are now automatically applied upon issue creation.However, a few inconsistencies have arisen in the past few months as new labels and GitHub actions have been implemented.
In this issue, I will detail actions that can be taken to organize and standardize labels to improve your workflow (especially with over 600 open issues!)
Important
Some of these changes will require edits to files such as label-actions.yml. I have created two associated PRs: #3918 and #3919.
Delete or Replace
Some labels duplicate the function of existing labels, or should be replaced with a better label.
Bug
Fixed Interally
duplicate
Needs R&D
status: needs r&d
Categorize
The full list of labels is currently alphabetically disorganized. Sorting them into categories can clean this list up.
small
size: small
medium
size: medium
large
size: large
help wanted
topic: help wanted
mods
topic: mods
platform specific
topic: platform specific
polish
topic: polish
scoring
topic: scoring
chart editor
topic: chart editor
Color
Currently, Label Actions closes issues as not planned or complete for three
status
labels.Just like the label
status: rejected
, highlighting these auto-close labels with prominent colors will serve two functions:Note
I can't obtain the exact Hex codes for existing label colors, so I will describe them in the table.
status: needs r&d
status
color)status
status: resolved internally
status
color)status
status: resolved
status
color)status: duplicate
status
color)rejected
color)low priority
Tip
Refer to the table below to see which labels close issues when applied.
status: resolved
status: rejected
status: duplicate
Descriptions
Some labels do not currently have descriptions. Assuming that all changes before this section have been implemented, there are two labels that should be described.
potential duplicate
status: resolved internally
Updated Changes
potential duplicate
should be unlabeled from all issues and deleted now that Eric has removed the funny duplicate issue detector.Closing
Important
These changes should be replicated in the funkin.assets repo as well.
I believe that organization is essential for an improved workflow on GitHub.
Thank you for your time and consideration!
The text was updated successfully, but these errors were encountered: