-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[core] Improve GitHub label workflows #3680
Conversation
These are the results for the performance tests:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would propose we keep this bot, and restructure the labels at the same time
support - stackoverflow
. We renamesupport
to this in the X and Core repositories. We don't provide support on MIT content. We delegate it to the community, the bot is important to save us time. With the date picker components, we will use it more often. The same way the support questions on DataGrid should use it.support: question
. We renamequestion
to this in the X and Core repositories. This is so developers can ask valuable question to improve the experience with the product. Valuable is key on this one. Usually, such question turns into a bug, a docs, a discussion, an enhancement, or simply stay here close to build a knowledge base on GitHub. No botssupport - commercial
. This will be used by all the issues open with https://github.com/mui-org/material-ui-x/blob/master/.github/ISSUE_TEMPLATE/3.pro-support.yml. No bots.
593462f
to
243e753
Compare
I've updated this PR to handle the change of the labels, so |
support
label botsupport: Question
label
support: Question
labelsupport: question
label
support: question
labelsupport: StackOverflow
label
support: StackOverflow
labelsupport: StackOverflow
label
support: StackOverflow
labelThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have updated the description and changed a few more things
this issue appears to be a support request. | ||
|
||
For support, please check out https://mui.com/getting-started/support/. Thanks! | ||
For support, please check out https://mui.com/components/data-grid/getting-started/#support. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Later on, to move to: https://mui.com/x/getting-started/support/
This change is meant to improve the support workflow. We have:
support
tosupport: StackOverflow
to make it clear about what this is about. It's about fair value sharing. We give MIT components away for free. In exchange, MUI expects developers to give back by contributing. The expectation is not for maintainers to spend even more time to do others' work (when we apply this label), but for maintainers to process new contributions.question
tosupport: question
. This is similar to the above, but we find the question so valuable to answer that we take it in.support: commercial
label. It's unlikely that the community will provide a lot of help to each other on the MUI X Pro plan, and will clearly not happen on the MUI X Premium plan. We have to take this in. However, bug reports and features requests should go to the usual channels, so we are simplifying the issue template.