nodejs/node

Migration of the GitHub bot from our infra to GitHub actions

Open

Aperta il 20 dic 2023

Vedi su GitHub
 (6 commenti) (1 reazione) (0 assegnatari)JavaScript (117.218 star) (35.535 fork)batch import
buildhelp wantedmeta

Descrizione

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

Guida contributor

Tech stack
nodejsgithub actions
Dominio
devopsinfrastructureci cd
Tipo issue
refactor
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
4
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
over 1 week
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
active
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
mostly clear
Prerequisiti
Node.jsGitHub ActionsGitHub Bot features
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
30
Direzione di ricerca
The issue outlines three main features of the existing bot: ping code owners, update commit status from Jenkins, and relay Jenkins requests. To migrate, one should examine the scripts at nodejs/github bot (specifically scripts/node ping owners.js, lib/push jenkins update.js, scripts/event relay.js) and understand how they interact with GitHub API. Then plan to implement equivalent functionality as GitHub Actions workflows or JavaScript actions. The maintainer comments or linked PRs may provide further guidance; currently there are no assignees or linked PRs.