Show CI failure details to non-collaborator PR authors
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
Description
What is the problem this feature will solve?
CI is now only visible to collaborators. External contributors can see that CI failed, but not why, so they have to ask a collaborator to learn about the CI status.
What is the feature you are proposing to solve the problem?
If CI fails on a PR from a non-collaborator, have nodejs-github-bot post a short comment with the failure summary, failing test names etc.
Original idea by @RafaelGSS
This is also similar in spirit to #32306 from 6 years ago, but opening a new issue to bring visibility to this in light of the recent collaborator-only CI access change.
What alternatives have you considered?
- Ping a collaborator
- Write bug free code 🧠
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 locating the nodejs-github-bot entry point that handles CI results for pull requests and review how failure information is currently available. Done means that a non-collaborator PR author receives a short comment containing the failure summary and failing test names when CI fails.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ci-cd, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100