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
Add Chore
to allowed commit tags
#5880
Comments
I'm for the addition of this label. Would be nice to have an easy way to identify tech debt-ish issues. |
Would we also add a corresponding issue label (perhaps also "chore", to keep it simple)? |
We need to update Maintainer guide, bot and build script if we are adding a new label. |
👍 @ilyavolodin @alberto, I'd like to work on this, as it'd be a nice first issue for me, where I can get familiar with some of the team's tooling. Is that ok? |
@mikesherov Sounds good. Just need to wait a little bit for @nzakas to mark this as |
Oh and forgot about release script. I think there might need to be some modifications there to aggregate base log entries based on the new label (although I don't remember if the list of labels is supplied there or it's just aggregating everything that it finds, without caring what it is). |
@mikesherov 👍 welcome to the team! I looked at Someone else with permissions will have to create the label, too. |
@nzakas any chance I can get access to the repo for the eslint bot? |
The things that need to be updated are:
|
I created the label. Not sure why you couldn't @alberto, I need to double check the permissions setup. |
@nzakas Also we need to update Makefile.js so that |
@platinumazure oops, forgot about that. Added. |
@mikesherov are you working on this? |
Yup. I'll do it tonight. Thanks for the ping |
Cool. I just asked because we are already using the new tag, so it would be nice to have this soon. |
PR coming soon |
@nzakas looks like you already took care of the Documentation. |
As proposed in the chatroom, we could add a tag for internal tasks that don't have observable effect on user experience, such as refactoring, adding tests, removing unused code or general cleanup.
Here are a couple of PRs that would qualify for this.
@eslint/eslint-team opinions?
The text was updated successfully, but these errors were encountered: