nodejs / nodejs/node

Migration of the GitHub bot from our infra to GitHub actions

Open
#51,236 8 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

build help wanted meta never-stale
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:

@nodejs/actions @nodejs/github-bot

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.