I feel like starting with labels that somewhat match conventional commits would be good, with maybe a couple other utilities. So I'm going to use this issue to plan that out.
[ ] dependencies
[ ] feature
[ ] bug
[ ] documentation
[ ] code style
[ ] refactor
[ ] performance
[ ] testing
[ ] tooling
[ ] ci/cd
[ ] chore
[ ] security
[ ] happy
[ ] discussion
[ ] needs scope
[ ] wontfix
[ ] plz help
[ ] workflow (not the github kind)
For reference, these are the categories of conventional commits:
feat
fix
docs
style
refactor
perf
test
build
ci
chore
And these are the things that CC doesn't account for that I think are relevant to managing a project:
question / discussion
stuff that needs scope
stuff that won't change
accepting help on an issue
security (which may be better left off of an issue?)
I'm wondering right now if doing labels like chore:dependencies to match better with chore(deps) would make sense? There's still project level things to account for though.
I feel like starting with labels that somewhat match conventional commits would be good, with maybe a couple other utilities. So I'm going to use this issue to plan that out.
For reference, these are the categories of conventional commits:
And these are the things that CC doesn't account for that I think are relevant to managing a project: