tektoncd / tektoncd/pipelines-as-code
Store repository status/results in tektoncd/results
Open
Nobody has claimed this yet.
bug
priority/low
- Dominant language
- Go
- Stars
- 214
- Forks
- 144
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 27
Description
We currently store repo statuses in the Repo CR, which is limited to 5 due of size and well limited.... it would be nice if we can store this in tektoncd/results and let the tools (cli/ui) fetch it directly from there
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 repository status is stored in the Repo CR and how the CLI and UI currently retrieve it. Then inspect the integration boundary with tektoncd/results; the work is done when results are stored there and both tools fetch them directly without the current repository-status size limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100