docs(README): document per-account service overrides (closes #117) - #170
Conversation
|
@coderabbitai review |
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 52 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. 📝 WalkthroughWalkthroughREADME.md now documents per-account service overrides—a feature allowing accounts to override global purchasing defaults (term, payment, coverage, enabled) for specific provider-service pairs. The section covers UI workflows, blank-field inheritance, an AWS-only V1 boundary, and the underlying API endpoint used by both UI and scripted setups. ChangesPer-Account Service Overrides Documentation
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
✅ Actions performedReview triggered.
|
c2c7a5e to
abb5d35
Compare
|
Rebased onto current |
|
✅ Actions performedReview triggered.
|
|
@coderabbitai full review |
✅ Actions performedFull review triggered. |
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
|
@coderabbitai full review |
✅ Actions performedFull review triggered. |
|
@coderabbitai full review |
✅ Actions performedFull review triggered. |
|
@coderabbitai full review |
✅ Actions performedFull review triggered. |
|
@coderabbitai review |
Rate Limit Exceeded
|
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
@coderabbitai full review |
✅ Action performedFull review finished. |
a95c724 to
e235425
Compare
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
@coderabbitai review |
✅ Action performedReview finished.
|
e235425 to
5022489
Compare
|
@coderabbitai review |
✅ Action performedReview finished.
|
Closes #117. Per-account service overrides have been a feature since migration 000011_cloud_accounts.up.sql (mid-2024) and now have full UI coverage via #72 (inline payment edit) and #106 (create modal). Adds a new "Per-Account Service Overrides" section to README between "Coverage Percentage" and "Safety Features" covering: - Concept + when to use vs the global Settings → Purchasing card. - Web-UI walkthrough (Settings → Accounts → expand → Service overrides). - AWS-only V1 boundary callout pointing at #109 for Azure/GCP. - How to edit existing overrides — inline Payment per #72, Reset, and the #110 follow-up for inline Term/Coverage/Enabled. - "Inherit" semantics: blank fields are not stored as a sentinel; the PUT request stays sparse and the engine reads the global default at evaluation time. - API parity note: the override modal targets the same endpoint as scripted setups; both write the same row. Also disables MD060 (table-column-style) in .markdownlint.yaml — same rationale as PR #169 (landing here too in case the PRs merge in a different order; both diffs are idempotent).
…I (refs #117) - Replace stale "#110 tracked / delete-and-recreate" limitation with the shipped reality: AWS overrides support inline edit of Term, Payment, Coverage, and Enabled directly on the row; non-AWS providers are read-only. - Rename "Reset" to "Delete" throughout the override-editing section to match the current button label and confirm dialog title (per #114).
…ide section - Replace the stale "AWS-only V1 boundary" callout with accurate text: the override modal is provider-aware and lists services for the account's provider (AWS, Azure, GCP). Issues #109 and #110 shipped and both the create modal and inline-edit work for all providers. - Replace "Non-AWS overrides display field values as read-only text" with the correct statement that all override rows support inline edit (Term, Payment, Coverage, Enabled). References to tracking issue #109 removed as it is closed. - Replace five U+2014 em-dashes in the new section with punctuation that matches the project prose style (semicolons, parentheses, period).
5022489 to
cc91cad
Compare
Summary
Closes #117.
Per-account service overrides have been a feature since migration
000011_cloud_accounts.up.sql(mid-2024) and now have full UI coverage thanks to #72 (inline payment edit) and #106 (create modal). None of it was documented, so users landing on the dashboard saw the panel + the Add modal with no narrative for what overrides ARE, when to use them, or how they interact with the global defaults.What's added
A new "Per-Account Service Overrides" section between "Coverage Percentage" and "Safety Features" covering:
.markdownlint.yaml
Disables MD060 (table-column-style) — same rationale as PR #169. Landing here too in case the PRs merge in a different order; both diffs are idempotent.
🤖 Generated with claude-flow
Summary by CodeRabbit