feat: Deployment ID + replay wrapper + anchors; docs+tests#92
feat: Deployment ID + replay wrapper + anchors; docs+tests#92flyingrobots wants to merge 12 commits intomainfrom
Conversation
feat(run): fun confirmation glyphs (🚢🪵 + ⚓️ when anchor, else ✅); honor SHIPLOG_CONFIRM_TEXT override refactor(run): simplify dry-run branch to single cmd_write call; dry-run still prints 'Would execute' and 'Would sign & append' previews
…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
…pports range/count, speed multiplier, step mode, and notes display
…h flag feat(verify/sign): surface concise reasons from git verify-commit and ssh-keygen; warn on suspicious command substitution tokens; alias --attach for --log chore(dev): add scripts/install-dev.sh symlink helper
…and --attach alias on write; warn on literal command-substitution tokens
- run: add --deployment flag/env; include deployment.id in trailer; mirror to ticket when missing - write: add --deployment flag/env; overlay deployment.id in trailer; ticket fallback - append: add --deployment flag/env; overlay deployment.id; ticket fallback
…lter - Docs: env (SHIPLOG_DEPLOY_ID), run/write/append flags, command-reference, replay usage - Replay: add --deployment / --ticket filter backed by export-json - Tests: stamp deployment.id, mirror ticket, and replay filter - Helper: scripts/shiplog-deploy-id.sh to mint IDs
… docs index and README Deployments & Replay section
- Add command pages: replay wrapper, anchor, deploy-id - Update README and docs index with links - Update feature docs: run/write/append/export-json/replay with deployment and anchor details - Update JSON schema doc to include optional 'deployment' object
…-pointer/--tag) and git shiplog anchor set|show|list; tests; README link updates
|
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 17 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 (27)
✨ 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".
| tip_sha="$(git rev-parse "$journal_ref" 2>/dev/null || true)" | ||
| if git rev-parse --verify "$anchor_ref" >/dev/null 2>&1; then | ||
| anchor_sha="$(git rev-parse "$anchor_ref")" | ||
| from="$anchor_sha" | ||
| [ -z "$to" ] && to="$tip_sha" | ||
| else |
There was a problem hiding this comment.
cmd_replay defaults to to the journal tip whenever --since-anchor is used (to="$tip_sha"). The wrapper later forwards this value as --to <tip> to scripts/shiplog-replay.sh, which constructs git rev-list <tip>..<ref>; when both arguments point at the same tip commit the rev-list is empty, so git shiplog replay --since-anchor always prints nothing even when entries exist after the anchor. Dropping the implicit --to (or using the anchor as the left side of the range) would allow the anchor replay to function.
Useful? React with 👍 / 👎.
1 participant
Adds --deployment/SHIPLOG_DEPLOY_ID with trailer deployment.id (mirrored to why.ticket when unset), git shiplog replay wrapper + script with --since-anchor/--pointer/--tag, and anchor set|show|list. Includes docs and tests.