Skip to content

ci(sdk-pr-review-gate): green when the agent RAN on the latest commit, not only when it passes - #202

Merged
kamal-kaur04 merged 2 commits into
mainfrom
feat/pr-review-gate-mandatory-run
Sep 16, 2026
Merged

kamal-kaur04 merged 2 commits into
mainfrom
feat/pr-review-gate-mandatory-run

Conversation

@rounak610

Copy link
Copy Markdown
Collaborator

What is this about?

Rolls out the mandatory-to-run gate change (SDK-7256) — the gate check now greens when the SDK PR Review Agent has run on the PR's latest commit (any verdict), not only when it passes; verdict advisory. Piloted on browserstack-node-agent#2574. CI/workflow only.

Related Jira task/s

https://browserstack.atlassian.net/browse/SDK-7256

Release (mandatory for every PR — required for the ready-for-review label)

Version bump: (required — tick exactly one)

  • minor (backwards-compatible feature)
  • patch (bug fix or other small change)

Release notes type: (optional)

  • New Feature
  • Bug Fix
  • Other Improvement

Release notes (customer-facing): (optional but encouraged)

  • N/A — CI/workflow-only change; no customer-facing or package impact.

Release notes (internal): (required — engineer-facing; what actually changed / why)

  • The gate required check now turns green as soon as the SDK PR Review Agent has posted a verdict marker for the PR's current head commit (any verdict: success | failure | pending), instead of requiring state=success. Verdict is advisory; a new commit turns it red until the agent re-runs. Closes the RCA-1320 gap (PR merging with no review) without the never-goes-green friction. Same one-line change piloted on browserstack-node-agent#2574.

Checklist

  • Ready to review
  • Has it been tested locally?

PR Validations

Run Tests: Comment RUN_TESTS to trigger sanity tests.

…, not only when it passes

Rolls out the "mandatory to run, not to pass" gate change (SDK-7256) — the same one-line
change piloted and validated on browserstack-node-agent#2574. The `gate` required check now
turns green as soon as the SDK PR Review Agent has posted a verdict marker for the PR's
CURRENT head commit — ANY verdict (success | failure | pending) — instead of requiring
state=success. The verdict is advisory; QA uses the green label to decide on merge. A new
commit turns it red until the agent re-runs on that commit.

Closes the RCA-1320 gap (a PR merging with no review at all) without the "endless comments /
never goes green" friction. CI/workflow only — no runtime or package change; marker parsing,
the ready-for-review label requirement, and the Slack/branch-protection wiring are untouched.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@rounak610
rounak610 requested a review from a team as a code owner September 16, 2026 08:59
@coderabbitai

coderabbitai Bot commented Sep 16, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited), Workspace UI (inherited)

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: a92e0b4e-8135-4e10-9351-354f3914073d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

@kamal-kaur04
kamal-kaur04 merged commit 503780d into main Sep 16, 2026
11 of 13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants