💡 GitHub Actions ideas

[nicolo-ribaudo]

• [ ] Automatically publish a Babel release to npm and generate the github changelog when a new v* tag is pushed. (I'm already experimenting with this) Changelog generation at https://github.com/babel/babel/pull/9434

• [ ] Remove the i: needs triage issue label when someone from the team comments.

• [ ] If @babel/types's definitions folder is updated but the generated builders/validators don't match, fail a PR status check and comment that the user (or a maintainer) can comment "@babel-bot update generated types". If it does, generate them and commit them to the PR.

• [ ] Automatically regenerate @babel/types docs on the website when the package is updated. (https://github.com/babel/website/issues/1680, https://github.com/babel/babel/pull/9245#pullrequestreview-190293914) Depends on https://github.com/babel/website/pull/2080

• [ ] When someone comments in a PR, for example "@babel-bot pack preset-env and parser", it should generate a tarball of those two packages and comment how to use them using yarn's resolutions package.json key. The .tar can be stored as an artifact on GitHub actions. Similar to https://github.com/microsoft/TypeScript/pull/30829#issuecomment-533846730

• [ ] Automatically remove "+1" comments (currently done by @babel-bot)