Repository navigation
fix(feature-ideation): discussion→dispatch redispatch bridge in the template - #550
Conversation
…he template Mirrors combsmith/.github-private#971 (#963) onto the org caller-stub template so every adopting repo inherits the fix: claude-code-action aborts on `discussion` event contexts, so `discussion: created` now goes through a `redispatch` job (guarded ideas/non-bot, PAT-required) that re-invokes the workflow via workflow_dispatch with `target_discussion`. The `ideate` reusable call runs only on workflow_dispatch/schedule. Pattern mirrors initiative-planner #618. Without this, new human Ideas crash with "Unsupported event type: discussion" and are never enhanced on creation. The .github-private stub already has the fix (#971); this propagates it to the fleet. Refs .github-private#963, #875, #872. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Review limit reached
More reviews will be available in 6 minutes and 27 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: ASSERTIVE 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 |
There was a problem hiding this comment.
Code Review
This pull request implements a redispatch bridge in the feature-ideation.yml workflow to bypass limitations with discussion event contexts. A new redispatch job intercepts discussion: created events and triggers a workflow_dispatch run with the discussion number passed as target_discussion. The main ideate job is updated to run only on non-discussion events, utilizing the new input. There are no review comments, so no further feedback is provided.
Dev-Lead — review-changes (applied)Changes committed and pushed. |
|
Dev-Lead — review-changes (no-changes)No changes were needed for this PR. |
|
@donpetry-bot review |
|
@don-petry I'm on it — starting a fresh review now. Results will appear in a few minutes. |
donpetry-bot
left a comment
There was a problem hiding this comment.
Automated review — APPROVED ✓
Risk: LOW
Reviewed commit: b37b7b6eb3d7822553c0b2dfa15c9574c9325074
Review mode: triage-approved (single reviewer)
Summary
Single-file change to the org caller-stub template standards/workflows/feature-ideation.yml (+48/-13). Adds a discussion → workflow_dispatch redispatch bridge so new human Ideas (Discussions) are enhanced without hitting claude-code-action's 'Unsupported event type: discussion' abort. Mirrors the established initiative-planner #618 pattern. Triage already cleared this as low-risk; this is a confirmation review and the assessment holds.
Linked issue analysis
No closingIssuesReferences — the PR uses Refs .github-private#963, #875, #872 (non-closing). The stated goal (propagate the #963/#971 discussion-context bridge fix to the org template) is fully reflected in the diff: a new redispatch job, a new internal target_discussion input, and the ideate job gated to non-discussion events.
Findings
No blocking findings. GitHub Actions security posture is sound:
redispatchjob runs withpermissions: {}(least privilege).- Untrusted-context values are passed via
env:(DISCUSSION_NUMBER,REPO) and referenced as shell vars — no${{ }}interpolation insiderun:, so no script-injection surface (the discussion number is an integer regardless). - PAT guard fails fast if
GH_PAT_WORKFLOWSis absent (a workflow_dispatch fired with GITHUB_TOKEN silently never starts — correct rationale). - No re-dispatch loop:
redispatchonly fires ondiscussion,ideateonly on non-discussion; the dispatched run takes theideatepath. - No hardcoded secrets (only
secrets.GH_PAT_WORKFLOWSreference). Secret-scanning MCP tool unavailable this session; CI gitleaks check passed.
Comments are accurate and the 'Do not edit this line' guidance is preserved.
CI status
All required checks green or appropriately skipped. SUCCESS: CodeQL (Analyze actions), SonarCloud (Quality Gate passed, 0 new issues), Secret scan (gitleaks), ShellCheck, Lint, Agent Security Scan, AgentShield, Feature Ideation Tests (lint/schema/bats), Dependency audit, CodeRabbit. SKIPPED: dependabot-automerge, ci-relay, and non-applicable language audits. gemini-code-assist reviewed with no actionable comments; coderabbit/codex were rate/usage limited (non-blocking). mergeStateStatus BLOCKED only because human review (org-leads) is still required.
Reviewed automatically by the PR-review agent (single-reviewer mode: fable 5). Reply if you need a human review.



Propagates the #963/#971 bridge fix to the org caller-stub template so every adopting repo inherits it —
discussion: createdredispatches toworkflow_dispatch(claude-code-action aborts on discussion contexts), mirroring initiative-planner #618. Without it, new human Ideas crash with 'Unsupported event type: discussion'. Refs.github-private#963, #875.