CI comment ends up in wrong repo
Open
Nobody has claimed this yet.
ci-public
never stale
- Dominant language
- Jinja
- Stars
- 542
- Forks
- 185
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 4
Description
I kicked off CI for https://github.com/nodejs/quic/pull/157 (https://ci.nodejs.org/job/node-test-pull-request/25909/) but the bot commented the CI link on https://github.com/nodejs/node/issues/157.
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 with the linked CI job 25909 and compare the originating quic pull request 157 with the node issue 157 where the comment appeared. Trace how the CI result is associated with a repository and pull request; done means the CI link is posted to the originating quic pull request rather than the node issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100