babel / babel-bot

🤖 A helpful bot to automate common tasks on Babel Issues/PRs

The compiler for writing next generation JavaScript.

Supporting Babel

Babel (pronounced "babble") is a community-driven project used by many companies and projects, and is maintained by a group of volunteers. If you'd like to help support the future of the project, please consider:

• Giving developer time on the project. (Message us on Twitter or Slack for guidance!)
• Giving funds by becoming a sponsor on Open Collective or GitHub (which goes to our Open Collective account)!

Sponsors

Our top sponsors are shown below! [Become a sponsor]

Intro

Babel is a tool that helps you write code in the latest version of JavaScript. When your supported environments don't support certain features natively, Babel will help you compile those features down to a supported version.

In

// ES2020 nullish coalescing
function greet(input) {
  return input ?? "Hello world";
}

Out

function greet(input) {
  return input != null ? input : "Hello world";
}

Try it out at our REPL.

FAQ

Who maintains Babel?

Mostly a handful of volunteers, funded by you! Please check out our team page!

Is there a Babel song?

I'm so glad you asked: Hallelujah —— In Praise of Babel by @angus-c, audio version by @swyx. Tweet us your recordings!

Looking for support?

For questions and support please join our Slack Community (you can sign up here for an invite), ask a question on Stack Overflow, or ping us on Twitter.

Where are the docs?

Check out our website: babeljs.io, and report issues/features at babel/website.

Want to report a bug or request a feature?

Please read through our CONTRIBUTING.md and fill out the issue template at babel/issues!

Want to contribute to Babel?

Check out:

• Our #development Slack channel and say hi! (sign-up)
• Issues with the good first issue and help wanted label. We suggest also looking at the closed ones to get a sense of the kinds of issues you can tackle.

Some resources:

• Our CONTRIBUTING.md to get started with setting up the repo.
• Our discussions/notes/roadmap: babel/notes
• Our progress on TC39 proposals: babel/proposals
• Our blog which contains release posts and explanations: /blog
• Our videos page with talks about open source and Babel: /videos
• Our podcast

How is the repo structured?

The Babel repo is managed as a monorepo that is composed of many npm packages.

License

MIT

babel-bot's Issues

Move to Probot

https://github.com/probot/probot

Should use the framework instead of our own thing

Add assignee (reviewer) to PRs

The Facebook/mention-bot offers a programmatic API (source).

It think we could easily integrate it in the Babel-bot.

Usage example:

mentionBot
  .guessOwnersForPullRequest(
    'https://github.com/babel/babel', // repo
    65, // pull request number
    'babel-bot', // user that created the pull request
    'master', // branch
    { maxReviewers: 3 }, // config
    [...]
  )
  .then(function(users) {
    // array with user names which should be included in review
    console.log(users);
  })
  .catch(function(err) {
    console.error(err);
  });

It will be triggered in src/handlers/pull_request/opened.js.

Instead of babel/babel#5057

Add a comment on PR with link to release

Ref original request babel/babel#1857

Auto label issue with "triage"?

eslintbot added the triage label x days ago

Basically each label starts off with triage and then when someone adds anything else it automatically gets removed?

Maybe not necessary but it might work well if we want it

Don't add "new issue" comment if user has submitted more that X issues

TBD: What is x. 3 maybe?

[Question] vscode configuration

Do we need Visual Studio Code configuration (.vscode) ?

[Question] Bot behavior in 2016

In babel/babel#4019, why does @babel-bot repeat comments originally made by others? Where do they come from?

Add babel-bot to the Babel org

The bot (hzoo there) is talking to itself.

The condition to skip the message is here, the user must be in Babel's org.

See babel/babylon#420 (comment)

PR Opened: Label if package.json updated

Basically signal that dependencies changed

• add a package
• remove a package
• upgraded a package, etc

similar in idea to #1

basically check the package.json of each folder in packages/x and then would need to parse if it's in devDeps and whether the line was added/removed, changed

Command to add issue/PR to a card in a project

Some GH docs:
https://developer.github.com/v3/projects/cards/

Update prod to Node.js v6.10

AWS Lambda supports v6.10 now.

Comments twice on PR with link to repl

see: babel/babel#6160

might be because there is a travis-branch job and PR-job

Update test failure message and behavior

Switch to editing message if one already exists to prevent message spam.

We can probably shorten the message to something like:

Hey @existentialism! It looks like one or more of your builds have failed. I've copied the relevant info below to save you some time.

• node v6 - linux
• node v4 - linux
• node v0.12 - linux

Core members

If someone is part of the org (or maybe specifically on the core team), add a label to the PR to prioritize! via @jridgewell

Could do something similar for issues

Reverse Greenkeeper

Send a PR (at least to Babel org projects, and maybe babel plugins) to update to the latest version with a PR, automatically.

• pr our projects
• pr canary build (either to either repo as smoke test, or to our own fork)

Nice to Have:

• Run a codemod if upgrading from 5 to 6, 6 to 7 (if necessary)

Run `eslint --fix` when requested

I would like to be able to comment "@babel-bot Fix lint!" and it automatically runs eslint --fix and prettier in a PR.

Auto-Labeling PRs with packages touched in the monorepo

I have a (working) implementation of this done locally, but there are a few decisions we need to make.

1. Do we have a cutoff (don't label if over X total packages touched)?
2. Should we not add the label for some use-cases (example: changing only READMEs or package.json)

Input wanted.

extraneous double quotes at end of posted comment on issues

babel-bot posted a comment on my issue here: babel/babel#12513 (comment). It contains an extraneous " at the very end:

[...] for an invite."

I traced through the code and I don't see where it would be coming from, since the string looks fine here and it's passed around without manipulation all the way to the GitHub API request. 🤷🏼

Close issue after no response for x days

One option is that we add the awaiting reply label to an issue and if no response after x days we close it.

Or a little differently, we wait x days for the bot to auto comment this will be closed in y days if no response, and if it's a support question ask on slack and not an issue.

PR Opened: Remove Label after Has PR is added

Add Has PR label to issues that have been referenced in a PR

After

babel-bot/src/handlers/pull_request/opened.js

Line 46 in 635399d

const requests = issues.map(id => github.addLabels(

Remove help wanted label

---

Same if someone claims an issue?

help-wanted -> claimed -> Has PR?

Update yarn.lock if package.json has been updated

This doesn't have to be done by the bot since it can run after CI but just wanted to note it here.

https://github.com/devtools-html/debugger.html/blob/master/bin/update-yarn-lock-file

Can I get more info around setup?

Hi,
In AWS_SETUP.md you have GitHub step that shows how to create new API Token thus giving repo permission. And in the final step, you mention about adding Environment variables such as GITHUB_API_KEY and GITHUB_SECRET from Github step. Where is that defined in Github step? What is API_KEY and SECRET referring to?

Thanks,
Suhas

[Partially done] Add `pr-opened` label to issues when a pr is opened that fixes/refs the issue

why: to make it easy to see which issues already have someone working on them

• maybe even signal the relevant pr somehow (if active, active x days ago)

name could be different just a suggestion

Parse

1. just the "fixed tickets" line in our pr template
2. anything that looks and smells like github ID # and is an issue
3. (1 || 2) + title of the ticket

Idea: validate new user PRs on website

Just spitballin', but we can check for correct image size, format, and auto-optimize.

Remove +1, -1

facebook/react-native#12542 (comment)

bonus: replace with reactions

Automatically deploy babel-bot from master

• Create IAM credentials with bare minimum amount of access
• Add credentials to Travis as AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables (ideally in the UI so there's no risk of leakage, but encrypted in travis.yml is OK too)
• Run ./scripts/deploy.js after building, on commits to master (NOT for PRs)

You might need to adjust deploy.js a bit, I made some assumptions when writing it (region is us-west-1, function name is BabelBot) that might not actually be true.

Don't reply with new issue comment when user opening issue is a member of Babel org

Twitter: hook up the bot to tweet out a message calling for help when `beginner-friendly` issue is created

Only when created or also updated?

Can discuss what the message should be here.

BTW if we do this we need to make sure we have a good template or set of steps for people to follow

Remove test fail message when tests work again.