Migration of the GitHub bot from our infra to GitHub actions
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading scripts/node-ping-owners.js, lib/push-jenkins-update.js, and the referenced scripts/event-relay.js entry point in nodejs/github-bot. Map each listed feature to a proposed GitHub Actions or Jenkins implementation, clarify the event-relay use with collaborators, and treat the migration as done when the bot's required features work without its old Debian host.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript, node.js
- Domain
- ci-cd, devops, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100