4 ms·
Thanks for the comment. Its always cool to see gitlab comments sharing insights that would be hidden by other companies. Off topic but while you are here I was
by Polylactic_acid 7y ago
Thanks for the comment. Its always cool to see gitlab comments sharing insights that would be hidden by other companies.
Off topic but while you are here I was wondering if gitlab would consider having the bot that tags issues as open for community contributors not tag issues on enterprise edition features since community members are unable to develop on these and it makes it hard to find issues that are actually open for the community to contribute to.
- sytse 7y agoThanks for asking. Right now we have one label accepting merge requests and then labels by tier. Does it work to filter on two labels? Or are we not consistent in labeling the tier? Another option would be to have an accepting merge request label per tier. But this might cause other problems, such as getting out of date when we change the tier before the feature is made.
- Polylactic_acid 7y agoI just had a look through some of the recent issues with the accepting merge request label and most of them refer to enterprise edition issues but only a small number have the label "enterprise edition". Many of them have other tags like "Category:Epics" but there seem to be a very large number of these EE edition labels making it not simple to just filter out enterprise edition features.
- rpaik 7y agoThanks for pointing that out. I've also seen missing "enterprise edition" labels in some MRs and can make a request to GitLab team members not to forget about the enterprise label.