nextcloud-libraries
[RFC] Remove `feature: *` labels
We have 37 feature: * labels.
- They are not used in any automations like CHANGELOG generation
- There is no control of having the correct label, we only have it sometimes
- Using them in search is not very reliable (see 2)
Thus I don't see a profit of having them. While they increase the list of labels twice and add an additional yet optional work during PR creation.
Proposal: remove these labels.
Assigning to myself. If the issue isn't' blocked in a month, I'll remove the labels.
Proposal: remove these labels.
Agree - but make sure that all issues assigned such a label can be found by title (e.g. prefix with [componentname]).
For PRs I think we should keep conventional commits with scope like feat(NcButton): ... so no label is needed there.
I don't have a strong opinion. Do what ever works best for you.
Agree - but make sure that all issues assigned such a label can be found by title (e.g. prefix with
[componentname]).
What's the benefit of having a prefix over a label? It seems to have the same problems as the labels while adding the possibility to come up with new inconsistent prefixes and mistyping them.
If we need to find issues by component name I think we should either rely on fulltext search or have labels for the components and use them consistently.
What's the benefit of having a prefix over a label? It seems to have the same problems as the labels while adding the possibility to come up with new inconsistent prefixes and mistyping them.
Well I could also live with labels, but something to search would be good. Labels need to be maintained that is what currently is not working in my opinion - so if we find a good other solution or a way to keep it up to date that would be great.
What's the benefit of having a prefix over a label? It seems to have the same problems as the labels while adding the possibility to come up with new inconsistent prefixes and mistyping them.
It is simpler. You only need to write where you are already writting a title instead going to another config item and possibly create a new label with the correct color.
In PRs we de-facto force the conventional commit style, which usually has the component name.