fix(changelog): disable persist-credentials so the sync PR can push#103
Conversation
The dispatch test got past auth into git, then failed with `remote: Duplicate header: "Authorization"` / HTTP 400. actions/checkout persists the token in the local git config, and create-pull-request adds its own; git then sends two Authorization headers. create-pull-request documents persist-credentials: false as the fix. This was the actual blocker behind the 400 — the token and permission changes in #102 were necessary but not sufficient. Found by running the workflow end to end.
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
|
Warning Review limit reached
Next review available in: 36 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✨ 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 |
2 participants
Third and final blocker in the changelog auto-PR chain, found by running the workflow end to end.
After #102 fixed the token, the dispatch test failed with
remote: Duplicate header: "Authorization"→ HTTP 400.actions/checkoutpersists its token in git config andcreate-pull-requestadds its own, so git sends two auth headers. The action documentspersist-credentials: falseas the fix.The generate step has succeeded in every run — only the push/PR step was blocked. This unblocks it.
Test plan