chore: replace git-chglog automation with git-cliff#767
Conversation
|
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: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (8)
✨ 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
git-chglog(Go) withgit-cliff(Rust) for changelog and release-note generation, mirroring the setup intxpipe/dolosfor cross-repo consistency.cliff.tomlat the repo root (copied from dolos) with conventional-commit parsers and emoji-grouped sections.git cliffintocargo releasevia[workspace.metadata.release]so future releases regenerateCHANGELOG.mdautomatically as a pre-release-hook.orhun/git-cliff-action@v4(--latest --strip header) — no more Go toolchain install.CHANGELOG.mdso existing history matches the new format.Test plan
cliff.tomlparses:git cliff --latestlocallyReleaseworkflow renders sensible notes when the nextv*tag is pushedcargo release --workspace --execute=falseto confirm the pre-release-hook fires