Skip to content

Format command output for terminal workflows #64

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
brdv merged 1 commit into from
Jul 24, 2026
Merged

Format command output for terminal workflows #64

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions USAGE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,20 @@ If installed via Homebrew, the Git subcommand entrypoint also works:
git stck <command>
```

## Output Behavior

When attached to a terminal, `stck` uses concise progress indicators for
long-running Git and GitHub operations. Durable `stck`, `git`, and `gh` lines
have distinct labels, and successful subprocess chatter is hidden.

If a subprocess fails, its captured stdout and stderr are printed in a labeled
diagnostic block. Git recovery instructions remain visible below that block.

Redirected output and CI logs never contain spinners or ANSI escape sequences.
The established line-oriented command, error, and `Summary:` formats remain
stable for grep-based workflows. Set `NO_COLOR` to retain the interactive
layout without color.

## Typical Flow

### 1. Inspect current state
Expand Down
Loading
Loading