tektoncd / tektoncd/pipelines-as-code
Mark skipped PipelineRuns as successful on GitHub
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 214
- Forks
- 144
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 27
Description
If a Check suite is marked as required on GitHub it must report successful result. Currently there is no option to mark the Check suite as skipped (see https://github.com/orgs/community/discussions/13690). Perhaps a configurable option could be added to PaC to mark the Check suite as successful even though the PipelineRun was skipped.
What we're trying to do is not to run pipelines for changes that are unrelated to the pipeline in question, using pipelinesascode.tekton.dev/on-cel-expression annotation and we would not like to make the check suite not required as then the changes could get merged even though the pipeline failed.
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 tracing how the on-cel-expression annotation causes a PipelineRun to be skipped and how GitHub Check suites receive their result. Define the configurable behavior so skipped PipelineRuns can report success while failed pipelines remain unsuccessful; done means required GitHub checks pass for unrelated changes without weakening failure checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100