Skip to content
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

Closed
alberto opened this issue Apr 17, 2016 · 18 comments
Closed

Add Chore to allowed commit tags #5880

alberto opened this issue Apr 17, 2016 · 18 comments
Assignees
Labels
accepted There is consensus among the team that this change meets the criteria for inclusion archived due to age This issue has been archived; please open a new issue for any further discussion build This change relates to ESLint's build process enhancement This change enhances an existing feature of ESLint

Comments

@alberto
Copy link
Member

alberto commented Apr 17, 2016

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?

@eslintbot eslintbot added the triage An ESLint team member will look at this issue soon label Apr 17, 2016
@alberto alberto added build This change relates to ESLint's build process evaluating The team will evaluate this issue to decide whether it meets the criteria for inclusion enhancement This change enhances an existing feature of ESLint and removed triage An ESLint team member will look at this issue soon labels Apr 17, 2016
@kaicataldo
Copy link
Member

kaicataldo commented Apr 17, 2016

I'm for the addition of this label. Would be nice to have an easy way to identify tech debt-ish issues.

@platinumazure
Copy link
Member

Would we also add a corresponding issue label (perhaps also "chore", to keep it simple)?

@ilyavolodin
Copy link
Member

We need to update Maintainer guide, bot and build script if we are adding a new label.

@mikesherov
Copy link
Contributor

👍 @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?

@ilyavolodin
Copy link
Member

@mikesherov Sounds good. Just need to wait a little bit for @nzakas to mark this as approved, but since he is the one who proposed it, I don't see a problem with it. Also, bot is currently not open sourced, so @nzakas will have to make that change. Everything else is up for grabs

@ilyavolodin
Copy link
Member

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).

@alberto
Copy link
Member Author

alberto commented Apr 18, 2016

@mikesherov 👍 welcome to the team!

I looked at eslint-release and it doesn't look like any changes are needed.

Someone else with permissions will have to create the label, too.

@mikesherov
Copy link
Contributor

@nzakas any chance I can get access to the repo for the eslint bot?

@nzakas nzakas added accepted There is consensus among the team that this change meets the criteria for inclusion and removed evaluating The team will evaluate this issue to decide whether it meets the criteria for inclusion labels Apr 18, 2016
@nzakas
Copy link
Member

nzakas commented Apr 18, 2016

I created the label. Not sure why you couldn't @alberto, I need to double check the permissions setup.

@platinumazure
Copy link
Member

@nzakas Also we need to update Makefile.js so that npm run check-commit will accept the new label, or has that been done already?

@nzakas
Copy link
Member

nzakas commented Apr 18, 2016

@platinumazure oops, forgot about that. Added.

@alberto
Copy link
Member Author

alberto commented Apr 21, 2016

@mikesherov are you working on this?

@mikesherov
Copy link
Contributor

Yup. I'll do it tonight. Thanks for the ping

@alberto
Copy link
Member Author

alberto commented Apr 21, 2016

Cool. I just asked because we are already using the new tag, so it would be nice to have this soon.

@mikesherov
Copy link
Contributor

PR coming soon

mikesherov added a commit to mikesherov/eslint that referenced this issue Apr 22, 2016
@mikesherov
Copy link
Contributor

#5929 @alberto @nzakas review?

@mikesherov
Copy link
Contributor

@nzakas looks like you already took care of the Documentation.

@nzakas nzakas closed this as completed in 0023fe6 Apr 22, 2016
@eslint-deprecated eslint-deprecated bot locked and limited conversation to collaborators Feb 6, 2018
@eslint-deprecated eslint-deprecated bot added the archived due to age This issue has been archived; please open a new issue for any further discussion label Feb 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
accepted There is consensus among the team that this change meets the criteria for inclusion archived due to age This issue has been archived; please open a new issue for any further discussion build This change relates to ESLint's build process enhancement This change enhances an existing feature of ESLint
Projects
None yet
Development

No branches or pull requests

7 participants