tektoncd / tektoncd/pipelines-as-code
exclude merge commit from the last commit title
Open
Nobody has claimed this yet.
bug
cli
priority/low
- Dominant language
- Go
- Stars
- 214
- Forks
- 144
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 27
Description
we show the last merge commit in UI/pac describe :
storing it in the labels from the controller when creating the pipelinerun
but merge commit are not very interesting and we should get the first non merge commit....
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
Trace how the controller creates the PipelineRun and stores the last commit title in labels, then inspect the UI/pac describe path that displays it. Reproduce the merge-commit case and verify that the displayed title comes from the first non-merge commit; the issue does not name a specific file or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, 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