Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📝 WalkthroughWalkthroughDocumentation added to explain Enterprise Grid's parallel cycles feature, including setup instructions via Project Settings, behavior when overlapping cycles are active, handling of incomplete work items when cycles end, and consequences of disabling the feature after overlapping cycles exist. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/core-concepts/cycles.md`:
- Line 86: Update the earlier absolute statements that claim "only one cycle can
be active at a time" and "cycles cannot have overlapping dates" so they are
scoped as exceptions — e.g., prepend "By default," or add "when parallel cycles
are disabled" — ensuring every place where those rules are stated (the earlier
absolute claims on the page) is changed to the conditional phrasing to match the
new sentence about "With parallel cycles enabled"; keep wording consistent with
the new line about parallel cycles running simultaneously.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: a4ed9707-c6b2-4d3f-8c97-5745637a900a
📒 Files selected for processing (1)
docs/core-concepts/cycles.md
|
|
||
| ## Run parallel cycles <Badge type="warning" text="Enterprise Grid" /> | ||
|
|
||
| By default, only one cycle can be active at a time, and cycles cannot have overlapping dates. With parallel cycles enabled, you can run multiple cycles simultaneously with overlapping date ranges. This is useful when your team manages parallel workstreams — for example, a two-week sprint running alongside a longer release cycle. |
There was a problem hiding this comment.
Clarify this as an exception to earlier “no overlap / one active cycle” rules across the page.
This section is accurate, but the page still contains absolute statements earlier (e.g., Lines 19, 42, 61, and 145) that conflict with Enterprise Grid behavior. Please update those earlier lines to say “by default” or explicitly scope them to when parallel cycles are disabled, so the document is internally consistent.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/core-concepts/cycles.md` at line 86, Update the earlier absolute
statements that claim "only one cycle can be active at a time" and "cycles
cannot have overlapping dates" so they are scoped as exceptions — e.g., prepend
"By default," or add "when parallel cycles are disabled" — ensuring every place
where those rules are stated (the earlier absolute claims on the page) is
changed to the conditional phrasing to match the new sentence about "With
parallel cycles enabled"; keep wording consistent with the new line about
parallel cycles running simultaneously.
Description
Type of Change
Screenshots and Media (if applicable)
Test Scenarios
References
Summary by CodeRabbit