We should use GitHub Labels to improve customer and team member experience.
Motivation
Many big OpenSource repositories are using labels to better manage Issues and PRs.
Customers can filter by labels and find issues more quickly.
Also they provide meta info for readers.
Detailed Design
I personally using this setup of labels: prettier/plugin-pug/labels
But some of the labels doesn't really match with the purpose of this repo. Therefore we should collect different labels from similar repos/tools and define our own setup.
Also we should define if we want to used something like "scoped" labels and/or icons/emojis within labels.
Documentation
Labels can and should have applied descriptions.
Drawbacks
No.
Alternatives
Anarchy (no labels) 😂
Open Questions
Any questions?
Help Needed
Yes, we should think together about which labelset suit our needs.
Add and use GitHub Labels
Summary
We should use GitHub Labels to improve customer and team member experience.
Motivation
Many big OpenSource repositories are using labels to better manage Issues and PRs.
Customers can filter by labels and find issues more quickly.
Also they provide meta info for readers.
Detailed Design
I personally using this setup of labels: prettier/plugin-pug/labels
But some of the labels doesn't really match with the purpose of this repo. Therefore we should collect different labels from similar repos/tools and define our own setup.
Also we should define if we want to used something like "scoped" labels and/or icons/emojis within labels.
Documentation
Labels can and should have applied descriptions.
Drawbacks
No.
Alternatives
Anarchy (no labels) 😂
Open Questions
Any questions?
Help Needed
Yes, we should think together about which labelset suit our needs.
Frequently Asked Questions
Currently none
Related Discussions
Currently none