-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: add more labels to issues #4444
Comments
I think triage was a label for maintainers to filter issues that needed to be categorized.
|
It would be nice to have a triaging guide too :) I don't really have the time to look at every issue/PR, but when I do, I can't really triage since I don't know what many of the labels mean. Just as an example, when do we use a feature or Type: Enhancement label? I swear that only Type: Enhancement PRs automatically go into the draft release notes (see https://github.com/mermaid-js/mermaid/blob/develop/.github/release-drafter.yml), but PRs are auto-labelled with feature if they come from a branch called I'm sure there other people with triage permissions in the mermaid repo that don't triage since they don't know how to. And having a guide would make it easier to onboard new community members if they want to help with triaging. |
Looking at I upvote triaging guide! Or at least adding description to each label, adopting new ones, removing duplicates. I'm more than happy to contribute if you're willing. I would also suggest adopting the new As stated here from the author of
And by doing so it would be simpler and close to the current develop lifecycle to the contributors. Which results in cleaner labels, organized flow, less complexity, and much more! |
Totally agree. I've also felt that we have too many labels and no guidelines on how to use them. @knsv @ashishjain0512 @jgreywolf @mermaid-js/atlantians can anyone give us an idea of what the plans were for the labels? |
I have been trying to clean up the labels here and there. Removing some, adding others, etc. I dont think there is an official plan in place, and we just need to come up with one. As opposed to randomly making changes as I had been doing. In general, I am a fan of like things being with like things. This means categorizing labels together (as we have no with some of them)
I think the that "topic" ones we have now should go away. |
Currently, it's hard to search for issues based on their labels. And from #4227:
So by adding more labels, users and developers would be able to filter issues and contribute to stuff they're interested in or related to each other.
You could add more labels for better visibility. For example:
Parser
: issues related to the parsing and syntax of diagrams. It would be helpful since I'm working on it here, feat(parser): reimplement parser inlangium
instead ofjison
#4401.The text was updated successfully, but these errors were encountered: