nodejs/node

Migration of the GitHub bot from our infra to GitHub actions

Open

#51,236 opened on Dec 20, 2023

View on GitHub
 (6 comments) (1 reaction) (0 assignees)JavaScript (35,535 forks)batch import
buildhelp wantedmeta

Repository metrics

Stars
 (117,218 stars)
PR merge metrics
 (Avg merge 13d 4h) (233 merged PRs in 30d)

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

Research direction
Examine the existing GitHub bot code at https://github.com/nodejs/github bot to understand each feature (ping owners, Jenkins updates, event relay). Then design corresponding GitHub Actions workflows or composite actions that replicate the functionality. Consider using JavaScript actions or third party actions for integration with Jenkins.
Tech stack
javascriptnodejsgithub actions
Domain
devopsci cdinfrastructure
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGitHub ActionsJavaScriptNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55