Migration of the GitHub bot from our infra to GitHub actions

[targos]

Maintenance of the GitHub bot has become a problem. The machine it's running on is on a quite old version of Debian that doesn't support recent versions of Node.js and we have very few people who know and work on the bot's code (https://github.com/nodejs/github-bot).

I'd like to know if collaborators would be willing to help with a migration of the bot's features to GitHub actions and/or Jenkins plugins/scripts that talk directly to GitHub.

Those features are:

• Ping code owners when a PR is opened: https://github.com/nodejs/github-bot/blob/main/scripts/node-ping-owners.js
• Update GitHub commit status or post PR comments when Jenkins jobs are started / finished: https://github.com/nodejs/github-bot/blob/main/lib/push-jenkins-update.js
• Respond to some Jenkins requests by relaying them to GitHub: https://github.com/nodejs/github-bot/blob/0cfe624c138c033f9ba2cd9f4e6e42bc8610a327/scripts/event-relay.js#L10C40-L10C40 (not sure what this is used for)

@nodejs/actions @nodejs/github-bot

[marco-ippolito]

Arent these action already triggered by a github action, for example when a PR is opened?

[targos]

No, they're triggered by a github webhook.

[phillipj]

Chiming in with some historical context in case it would be helpful:

• Some ancient parts has already been pulled out of the github-bot into the Github Action node-pr-labeler, dunno if you feel it's a sensible project to continue building on
• Jenkins relay seemed like a sensible trick years ago to allow writing Github Actions based off of Jenkins events: nodejs/github-bot@9ef8f37

Regarding the last point, if Jenkins could talk directly with Github instead these days, that sounds reasonable for less indirection 👍🏻

[targos]

We can probably do something with https://github.com/jenkinsci/github-checks-plugin

[avivkeller]

Ping code owners when a PR is opened: https://github.com/nodejs/github-bot/blob/main/scripts/node-ping-owners.js

#53149
nodejs/github-bot#521