Auto-Labeling PRs with packages touched in the monorepo

[Andrew Levine]

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.

[Sven Sauleau]

Labels:

• experimental

  • Where packages matches /experimental/

• flow

  • Where packages matches /flow/

• cli (new)

  • Where packages matches /^babel-cli$/

• pkg: register

  • Where package matches /^babel-register$/

• pkg: traverse

  • Where package matches /^babel-traverse$/

• pkg: generator

  • Where package matches /^babel-generator$/

• react

  • Where package matches /react/

• tag: documentation

  • Where file changed matches /.*\.md$/
  • Where should be at least more than 5 lines changed (I think we don't need to label wording changes).

• tag: internal

  • Where packages matches /helper/ (if helper are considered as internal)
  • Where package matches /^babel-core/

• tests

  • Where file changed matches /test\/*.js/ (if helper are considered as internal)

---

• Multiples labels could be applied given the rules above.
• We could limit it to 5 labels.
• The minium amount of line changed could be set to 5.

[Henry]

Can you push the PR, I think the functionality is what we want and adding the labels later when we want to. An easy one is the react packages -> react or something like that