chore: set feature-ideation project_context to enable ideation - #460
Conversation
The caller stub still carried the stock TODO placeholder, so every scheduled run failed at the 'Validate project_context is customised' guard and no Ideas Discussions were ever produced. This fills in a real 3-5 sentence description of the project, its users, and the competitive landscape for Mary to research.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
don-petry
added
the
dev-lead:hands-off
|
Warning Review limit reached
Next review available in: 41 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 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 |
There was a problem hiding this comment.
Pull request overview
Updates the repo-local feature-ideation.yml caller to replace the placeholder project_context with a real project description, allowing the reusable ideation workflow’s customization guard to pass and scheduled ideation runs to succeed.
Changes:
- Replaced the
project_contextTODO placeholder with a concrete project/market description for ideation prompts.
Dev-Lead — review-changes (applied)Changes committed and pushed. |
|
* chore: set feature-ideation project_context (enable ideation) The caller stub still carried the stock TODO placeholder, so every scheduled run failed at the 'Validate project_context is customised' guard and no Ideas Discussions were ever produced. This fills in a real 3-5 sentence description of the project, its users, and the competitive landscape for Mary to research. * chore: dev-lead update (review-changes) [skip ci-relay] --------- Co-authored-by: donpetry-bot <281750570+donpetry-bot@users.noreply.github.com>
What
Fills in the
project_contextin this repo'sfeature-ideation.ymlcaller stub with a real 3–5 sentence description of the project, its target users, and the competitive landscape.Summary: MIT Gmail/Drive/Calendar productivity automation suite.
Why
The stub still carried the stock
TODO: Replace this…placeholder. The reusable workflow's "Validate project_context is customised" guard greps for that exact string andexit 1s, so every scheduled Friday run has been failing and the repo has produced no (or stale) Ideas Discussions:With a real
project_context, the guard passes and Mary (the BMAD analyst) can run the broad ideation scan. After merge, I'll dispatch a run to verify.Context sourced from the repo description / README / BMAD planning artifacts and the repo's prior April ideation output.
🤖 Generated with Claude Code