Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Feature Request] Add --no-progress flag for silent execution in VCS

Open
#1,991 1 comment 1 reaction 0 assignees View on GitHub

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

USER STORY
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)
Image
Workaround

Scroll... :)

Urgency

Low

Dominant language
TypeScript
Stars
240
Forks
52
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from forcedotcom/code-analyzer

All issues in forcedotcom/code-analyzer

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.