GH Label Cleanup #1134
Replies: 3 comments 4 replies
-
Thank you @alexanderbez for the label improvement ideas! I agree with the label structure for things like:
I don't think the I think we need to keep a good balance between labels and project's custom fields. I don't think we want too many labels or too many custom fields. Things like Thank you! |
Beta Was this translation helpful? Give feedback.
-
Can we remove the icons from labels or move them to the end of the label name? Makes it less trivial searching by labels when they are in the front |
Beta Was this translation helpful? Give feedback.
-
Per chain dev call, going with Thanks for this suggestion Bez! |
Beta Was this translation helpful? Give feedback.
-
I'd like to propose a bit of housekeeping and general cleanup to our Github label management. This is based on my experience that I've observed working with Tendermint, the Cosmos SDK and applications built on top.
To summarize
C:
which stands for component/categoryC:x/gamm
,C:x/epoch
,C:IBC
T:
which stands for typeT:Bug
,T:CI
,T:Security
,T:Docs
S:
which stands for statusS:backport/v7.x.x
,S:Blocked
,S:Pinned
P:
which stands for priorityP:High
,P:Medium
,P:Low
A:
which stands for actionA:Automerge
C
and purple forT
P:Critical
orT:Bug
And that's pretty much it. Ideally, we have no more than 30-40 labels if we do this correctly, maybe even less.
Examples:
Beta Was this translation helpful? Give feedback.
All reactions