tektoncd / tektoncd/pipelines-as-code
Re-run failed check triggers even success pipeline runs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 214
- Forks
- 144
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 27
Description
There is a feature addition to support check suite for GithubApp PR Ref: https://github.com/openshift-pipelines/pipelines-as-code/pull/1191
According to the feature
Expected Behavior:
Re-run failed checks : should re-run only failed PipelineRun
Re-run all checks: should run both failed and success PipelineRun
Current Behavior:
Re-run failed checks : re-running both failed and success PipelineRun
Re-run all checks: re-running both failed and success PipelineRun
cc @chmouel
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 reviewing the check-suite feature introduced in PR 1191 and trace how the GitHub App handles “Re-run failed checks” versus “Re-run all checks.” Confirm that failed checks rerun only failed PipelineRuns, while all checks rerun both failed and successful PipelineRuns; add or update coverage for both behaviors if the existing feature tests are found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100