[SUPERSEDED] Guard pull_request context in agent review kickoff job if#7
[SUPERSEDED] Guard pull_request context in agent review kickoff job if#7scalinity wants to merge 3 commits into
Conversation
Use job-level if, string workflow_dispatch input, and remove concurrency group that broke workflow file validation on push. Co-authored-by: Daniel Escalante <scalinity@users.noreply.github.com>
Co-authored-by: Daniel Escalante <scalinity@users.noreply.github.com>
|
Warning Review limit reached
More reviews will be available in 33 minutes and 10 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. 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)
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.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f808108b18
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| cancel-in-progress: false | ||
| pull-requests: write | ||
|
|
||
| jobs: |
There was a problem hiding this comment.
Serialize kickoff runs per pull request
When the same eligible PR gets two runs close together, such as a draft cursor/* PR being opened and quickly marked ready or a manual dispatch happening while the opened run is still in progress, both runs can call listComments before either creates the marker comment. The marker check is not atomic, and this commit removed the PR-scoped concurrency group that previously serialized those runs, so duplicate @codex/@claude kickoff comments can be posted. Please keep a concurrency group keyed by PR number with a workflow_dispatch-safe expression.
Useful? React with 👍 / 👎.
PR #7 is superseded: take main workflow (YAML-safe array.join, synchronize + edited triggers). Job-if guard already on main. Co-authored-by: Daniel Escalante <scalinity@users.noreply.github.com>
Agent review debateThis pull request was opened by an automated agent (Cursor Cloud Agent). Starting the cross-agent review thread so we capture findings before merge. @codex review @claude Please review this PR and engage with Codex's findings — agree or disagree on each P0/P1, note missing risks, and keep the debate in this thread before merge. Review focus (everybot)
Repo guidance: see Automated by agent-pr-review-kickoff.yml · PR: #7 |
|
To use Codex here, create a Codex account and connect to github. |
|
Closed via Close open pull requests workflow (team cleanup). |
Superseded — close without merging
This PR is obsolete. All changes (and more) are already on
main:array.joinfor@codex/@claudementions)synchronizetriggereditedtriggerThe job-level
ifguard from this branch is included in the current workflow onmain.Merge conflicts with
mainwere resolved oncursor/fix-kickoff-job-if-0cc0by takingmain's workflow file. Diff vsmainis empty — merging would only add redundant commits.Action: Close this PR.
Slack Thread