[Feature Request] Add --no-progress flag for silent execution in VCS
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- cli
Research direction
Start at the code-analyzer run CLI entry point and trace where percent progress is written to stdout. Confirm how the existing summary is emitted and identify the relevant CLI tests, if present. Done means a --no-progress or equivalent flag suppresses progress lines while preserving the summary output.
Written by the indexing model from the issue text.
Description
Product Area
The "code-analyzer" CLI
Your Need or Problem
When I run Code Analyzer in my GitHub workflow, I want to watch stdout but not see unnecessary lines.
When the analyzer runs, it has progress indicators - percent progress.
I'd like a way not to have that - I'd just like it to run and show that summary. That way we have fewer lines to scroll down.
Please add a --no-progress or similar flag so we save output lines.
Your Desired Solution
Please add a flag to code-analyzer run called --no-progress or even --silent so progress isn't shown to stdout.
Alternatives Considered
We may need to try clearing the output screen, but that feels cumbersome.
Additional Context (Screenshots, Files, etc)
Workaround
Scroll... :)
Urgency
Low
- Dominant language
- TypeScript
- Stars
- 240
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from forcedotcom/code-analyzer
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
forcedotcom/code-analyzer#2094 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
forcedotcom/code-analyzer#2093 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
forcedotcom/code-analyzer#2091 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
forcedotcom/code-analyzer#2090 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
forcedotcom/code-analyzer#2101 ·
All issues in forcedotcom/code-analyzer
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
MystenLabs/MemWal#1085 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
📕documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
db-ux-design-system/core-web#8343 ·
Maintainers usually reply within 1 day
-
enhancement triage/needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
heygen-com/hyperframes#4944 ·
Maintainers usually reply within 1 day
-
ai-driven-qa bug claude
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
linagora/twake-calendar-frontend#1493 · 1 comment ·
Maintainers usually reply within 1 day