You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
🤖 Limit git status output to reduce console spam (#258)
Reduces console noise from background git status polling by increasing
the bash truncate limit.
## Changes
### Increase bash truncate limit to 80 lines
Changed from 50 → 80 lines for the `truncate` overflow policy. This
provides better debugging context for git status output while still
preventing excessive spam.
**Before (50 lines):**
- Too restrictive for useful debugging
- Git status output often cut off mid-info
**After (80 lines):**
- Provides better context for git operations
- Still prevents console flooding
- Only affects IPC bash calls (background operations)
## Note on SHOW_BRANCH truncation
Initially considered truncating `git show-branch` output before parsing,
but this would break ahead/behind counting in
`parseGitShowBranchForStatus` which iterates all commit lines. The
80-line truncate limit is sufficient for most cases, and the `truncate`
overflow policy ensures we don't spam temp files.
## Dependencies
Built on top of #256 which adds the `overflow_policy` feature.
_Generated with `cmux`_
consterrorMessage=`[OUTPUT TRUNCATED - ${overflowReason??"unknown reason"}]\n\nShowing first ${maxTruncateLines} of ${lines.length} lines:\n\n${truncatedOutput}`;
0 commit comments