Bot comment on build failure
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 305
- Forks
- 148
- Avg merge
- 9h 2m
- Merged PRs (30d)
- 3
Description
(not when the job fails to start, but when the tests or build fails, so it wouldn't revert https://github.com/nodejs/github-bot/issues/238)
node-core-utils has this great tool ncu-ci pr, which can be used to get a list of failing tests. We could use the GitHub Bot to comment the result of ncu-ci pr back on the Pull Request when a build fails, so it's easier for folks to see which errors happened. Or the bot could edit it's own comment, to avoid notifications, but personally I would like to get notified (I understand folks might be opposed to it though).
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
The proposal centers on node-core-utils's ncu-ci pr command and the GitHub Bot; no repository file or test is named. First trace how build and test failures are received, then resolve whether the bot posts or edits a pull-request comment. Done means the chosen behavior reports the command's failing-test results only when a job starts but its tests or build fail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript, node.js
- Domain
- ci-cd, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100