Extract PR labelling into separate GitHub Action

[phillipj]

As already discussed in #264 and other threads here and there, we'd like to delegate as much as possible to the different repository contributors themselves, instead of having this github-bot being a bottleneck.

What we've been doing with the @nodejs-github-bot so far, by having the file paths -> labels configuration as code inside the github-bot' source code, has worked, but the downside of having to go into this repo and grasp how it works, to perform trivial labelling changes for the nodejs/node repository, isn't ideal for its contributors. It would be far better if they could be allowed to change a configuration file inside nodejs/node instead and for labelling to be done via a GitHub Action instead.

---

I'd like to jump onto copy-pasting most of what we have in the github-bot today, into a separate GitHub Action.

Don't hesitate to shout if anyone has ideas or already is on their way making this happen somehow.

[targos]

Huge +1 to that! I think a custom action in a new repository makes sense.

[phillipj]

Thanks for confirming the idea!

Forgot to mention that I skimmed through the existing Labeler Action source as its description matches exactly what we need: label PRs based on files being changed.

Although when comparing our existing rules to what the Labeler Action allows, it's not compatible. I wouldn't be surprised if we could have found a different ruleset for which we could have used Labeler, but that seems way more time consuming to me and involves a lot more people, than using what we've got, just applied differently (Node.js server vs GitHub Action).

[phillipj]

After some tweaking and adjustments to the github-bot code, extracted into node-pr-labeler as a GitHub Action, I've got a working proof-of-concept:

• local .github/pr-labels.yml config
• Pull Requests with labels

Before using this Action in nodejs/node, I'm assuming it'll be preferable if it were moved into the nodejs organisation.

@targos any chance you know the process of moving repos into the nodejs org?

[targos]

The process is documented here: https://github.com/nodejs/admin/blob/master/transfer-repo-into-the-org.md#transferring-an-existing-repository-into-the-organization

[phillipj]

Perfect, thx! I'll get to that after porting over the recent needs-ci label

…

On Sun, 14 Mar 2021 at 14:00, Michaël Zasso ***@***.***> wrote: The process is documented here: https://github.com/nodejs/admin/blob/master/transfer-repo-into-the-org.md#transferring-an-existing-repository-into-the-organization — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#294 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJMWE6IJJW6GKDHUIAAPALTDSXQBANCNFSM4YLHC6FA> .