ci: pass --allow-dirty to shipper publish/resume too#568
Conversation
#567 added --allow-dirty to `shipper preflight`, but the live publish run still failed: [1/53] Publishing uselesskey-aws-lc-rs@0.7.0... (1.533µs) Error: git working tree is not clean; commit/stash changes or use --allow-dirty `shipper publish` and `shipper resume` also check git cleanliness up- front. Add `--allow-dirty` to both invocations in `release.yml` and `publish-retry.yml` so the same `.shipper/plan.txt` output that the Plan step writes via `tee` doesn't trip the subsequent commands. This is the in-flight v0.7.0 unblock; the long-term fix (`.shipper/` already gitignored in #567, optionally writing the plan to a path outside the workspace) keeps applying from v0.8.0 onward.
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ 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. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ 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 |
Summary
#567 added `--allow-dirty` to `shipper preflight` but the live v0.7.0 publish run still failed at the publish step:
```
[1/53] Publishing uselesskey-aws-lc-rs@0.7.0... (1.533µs)
Error: git working tree is not clean; commit/stash changes or use --allow-dirty
```
`shipper publish` and `shipper resume` each do their own up-front git-cleanliness check. Add `--allow-dirty` to both in `release.yml` and `publish-retry.yml`.
The long-term hygiene fix (`.shipper/` in `.gitignore` via #567, or writing the plan to a path outside the workspace) already applies for v0.8.0+. This PR is the in-flight unblock for v0.7.0.
Test plan