feat: Skip frequent printing of user-friendly progress bars in CI jobs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8
- Forks
- 7
- Avg merge
- 17h 16m
- Merged PRs (30d)
- 2
Description
In workflows like the below, the progress bars frequently print status to the workflow output. The result in the end is that the workflow output is hard to read because there's so many similar log messages being printed to the terminal:
https://github.com/cilium/cilium/actions/runs/9946325024/job/27476554801#step:11:29
The progress bars are really handy when running the tool manually, but when run in a non-interactive environment it would be nice if it only printed a few messages - for instance, once for every 10% of progress made or if the estimated time to complete changes significantly since the last printed message (>20%).
Contributor guide
No contributing guide indexed for this repository
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 inspecting the linked Cilium workflow job and tracing which release tool emits the repeated progress-bar messages. Compare interactive and CI/non-interactive behavior, then verify that CI output is reduced while manual progress bars remain useful; the issue suggests reporting every 10% or when estimated completion changes by more than 20%.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100