eslint-github-bot
eslint-github-bot copied to clipboard
Plugin-based GitHub bot for ESLint
Bumps [moment-timezone](https://github.com/moment/moment-timezone) from 0.5.23 to 0.5.35. Release notes Sourced from moment-timezone's releases. 0.5.34 Updated data to IANA TZDB 2021e Release 0.5.33 Updated data to IANA TZDB 2021a Release 0.5.32 Updated...
The Pull Request section of the ESLint documentation explicitly mentions that > All ESLint projects follow [Conventional Commits](https://www.conventionalcommits.org/) for our commit messages[^1]. The convention for Conventional Commits is ``` [optional...
This is a tracking issue for the various updates we need to make to the bot for the new triage process (working on documentation right now and will link to...
e.g. https://github.com/eslint/eslint/pull/14010#issuecomment-761738132
It looks like the bot is adding the `auto closed` label and commenting on issues that are already closed. See https://github.com/eslint/eslint/issues/11859.
Example issue: eslint/eslint#11188 When the auto-close plugin closes an issue, it usually leaves a message saying we couldn't muster enough support for the change (with slight variations if the issue...
As suggested [here](https://gitter.im/eslint/eslint?at=5b5a74b6b9a1803f205e77b1), this would allow people who follow the issue to also keep up with discussion that moves to a PR. This would probably work by having the bot...
Currently auto-close only closes issue, however, if the issue was created to just be a front for the PR, that leaves PR orphan and make it harder to track. Examples...
When someone adds the `needs info` label, the bot's message is intentionally very generic, because we sometimes aren't sure what an issue is trying to do at all. However, there...
Though I'm not sure that it's possible. As our guideline, accepting enhancement requires a champion and three or more :+1:s. But it's not easy to know the issue status because...