Improve changelog automation prompt#9070
Conversation
|
Warning Review limit reached
More reviews will be available in 17 minutes and 40 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?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 credits. 🚦 How do rate 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 see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro 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 |
|
@coderabbitai full review |
✅ Action performedFull review finished. |
There was a problem hiding this comment.
Pull request overview
This PR updates the changelog generation script used by the docs repo workflow to (a) refine the AI system prompt used for release-note polishing and (b) improve Go version handling so the generated ### Go Version section includes a concrete version even when GO_VERSION isn’t provided.
Changes:
- Expanded the Claude system prompt with stricter formatting/terminology rules (including DM/GM expansion and one-section-per-note).
- Added helpers to normalize Go versions and to extract the previously documented Go version from the existing changelog when
GO_VERSIONis empty. - Updated feature-release anchors/headings to use the
-feature-releasesuffix and adjusted how the Go Version section is rendered.
Summary
DM→Direct Message,GM→Group Message), one-section-per-note rule, and a new instruction Test image #10 ("Focus")normalize_go_version()andextract_previous_go_version()helpers so the Go Version section always shows a concrete version number (looked up from the existing changelog whenGO_VERSIONis not provided)-feature-releasesuffix to match the ESR pattern, and includes the full release-policy URLCHANGELOG_PATHenv var is now read inmain()before building the Go sectiongo_sectionoutput changed from a bullet point to a bare sentence matching Mattermost changelog conventionTest plan
go1.22.5andv1.22.5input formats-feature-releaseanchor suffix🤖 Generated with Claude Code