feat(run): preamble streaming + docs (Customization)#91
feat(run): preamble streaming + docs (Customization)#91flyingrobots wants to merge 3 commits intomainfrom
Conversation
…end 🚢🪵✅/🚢🪵❌; prefix console lines with ' | ' while keeping raw logs
- Add preamble and confirmation controls to env reference - Update run/write/command-reference with preamble, glyph defaults, quiet mode - Note default --no-verify pushes in write/publish docs - Link env reference from docs index
…s, auto-push notes) and link to env reference
|
Warning Rate limit exceeded@flyingrobots has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 23 minutes and 21 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (6)
✨ Finishing touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| set +e | ||
| "${run_argv[@]}" > >(tee -a "$log_path") 2> >(tee -a "$log_path" >&2) | ||
| if [ $preamble -eq 1 ]; then | ||
| # Prefix console output with " | " while keeping raw logs in $log_path | ||
| "${run_argv[@]}" \ | ||
| > >(tee -a "$log_path" | sed 's/^/ | /') \ | ||
| 2> >(tee -a "$log_path" >&2 | sed 's/^/ | /') | ||
| else |
There was a problem hiding this comment.
When the preamble is enabled, the stderr stream is redirected with 2> >(tee -a "$log_path" >&2 | sed 's/^/ | /'). Because stdout is redirected to >&2 before the pipe, sed never receives the bytes, so stderr is emitted to the console without the | prefix while stdout is prefixed. Users enabling the feature will see inconsistent formatting and missed prefixes for warnings/errors. Redirect tee’s output through sed and back to stderr (e.g. 2> >(tee -a "$log_path" | sed 's/^/ | /' >&2)) so both streams are formatted consistently while logs remain raw.
Useful? React with 👍 / 👎.
1 participant
Adds TTY preamble streaming (🚢🪵🎬 … 🚢🪵✅/❌). Updates docs Customization. Tests for attach/warnings will land in a follow-up.