tektoncd / tektoncd/pipelines-as-code
Skipped user case creates a new checkrun
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 214
- Forks
- 144
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 27
Description
If CI has ran, PAC has created checkruns for the Pipelineruns and later if any unauthorised user comment
/retest or /ok-to-test PAC creates a new checkrun for skipped notification instead of using existing.
PAC should reuse existing because we can't delete a checkrun so once the CI is triggered by authorised
user, the checkrun will still be there and can't be removed
and we have 2 pipelineruns so one checkrun will be there with invalid details
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 issue names no files, tests, or entry points. Start by tracing how unauthorised /retest and /ok-to-test comments handle skipped notifications and existing checkruns; done means the authorised retry reuses the existing checkrun without leaving duplicate or invalid details.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100