Skip to content

ci: route owned branches and PRs to 5070X - #471

Open
2233admin wants to merge 2 commits into
mainfrom
ci/5070x-owned-branches-bda99e57998e
Open

2233admin wants to merge 2 commits into
mainfrom
ci/5070x-owned-branches-bda99e57998e

Conversation

@2233admin

@2233admin 2233admin commented Oct 22, 2026 •

Copy link
Copy Markdown
Owner

This changes compatible CI runner routing only. Same-repository branch pushes, manual runs and pull requests use the 5070X Linux/Docker pools and, after native acceptance, repository-bound Windows workers. External fork PRs retain their existing runner fallback and GitHub approval requirements. Unsupported platforms, publishing, deployment and workflow triggers remain unchanged. Required branch protection is not bypassed. Set CI_5070X_ENABLED=false to opt out.

@qodo-code-review

Copy link
Copy Markdown

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ⚠️ Failed 2026-10-22T14:26:23.053783Z
We couldn’t complete this review. Comment @codex review to try again.
13a5952 PR opened
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

@coderabbitai

coderabbitai Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 59 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 2d6f046a-77e6-4990-aa53-56112082dbff
📥 Commits

Reviewing files that changed from the base of the PR and between 13a5952 and e32920c.

📒 Files selected for processing: 3
  • .github/workflows/ci.yml
  • .github/workflows/codegraph-conformance.yml
  • .github/workflows/release.yml

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 1caae7d9-a5bb-4358-86a8-01f5c753cb20
📥 Commits

Reviewing files that changed from the base of the PR and between 6bc17f4 and 13a5952.

📒 Files selected for processing: 4
  • .github/workflows/ci.yml
  • .github/workflows/codegraph-conformance.yml
  • .github/workflows/release.yml
  • .github/workflows/skill-check.yml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📝 Summary

Summary by CodeRabbit

  • Chores
    • CI workflows now use the configured Linux runner for eligible Ubuntu jobs on pushes and manual dispatches across branches, as well as pull requests from the same repository.
    • Other event types, fork pull requests, and non-Ubuntu jobs continue to use their existing runners.

With CI_5070X_ENABLED enabled, several workflow jobs now use ci-5070x-linux for pushes and workflow dispatches on any branch, plus pull requests from the same repository. Other events and runner fallbacks remain job-specific.

Changes: Workflow runner selection

Layer / File(s) Summary
Expand dedicated runner conditions
.github/workflows/ci.yml, .github/workflows/codegraph-conformance.yml, .github/workflows/release.yml, .github/workflows/skill-check.yml
CI, conformance, release, and skill-check jobs now select ci-5070x-linux for enabled pushes and workflow dispatches on any branch, and for same-repository pull requests. Other cases retain their configured fallback runner.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Feature

Merge Risk: ⚪ Minimal · up to 13a59

The runner routing changes retain the documented fallbacks and are mergeable with normal CI checks.

Pre-merge checks: Passed 5
Check name Status Explanation
Title check Passed The title clearly summarizes the main change: routing owned branches and pull requests to the 5070X CI runner.
Docstring Coverage Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Description check Passed The description accurately describes the CI runner-routing changes, including same-repository events, fork pull request fallbacks, opt-out behavior, and unchanged workflow areas.
Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (4 skipped: 4 unsupported.)

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

❤️ Share

A rabbit checks the runner route,
Across each branch, it hops about.
When flag and event align just right,
The Linux runner comes in sight.
Other paths keep their fallback flight.

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

@github-actions

github-actions Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

Code Intel change risk

Score Percentile Level
52/100 29th (vs last 48 commits) 🟢 low

Top signals

  • Diff shape: 4 file(s), +7/-7 (max file share 0.43)
  • Test asymmetry: source changed, tests touched
  • Bug-magnet: 37 fix commit(s) in touched files (180d)
  • Churn: 71 commit(s) touching these files (90d)

revspec: origin/main..HEAD · threshold: score >= 80 blocks unless labeled risk-accepted; percentile is reported, not gated (#201) · code-intel change risk

@github-actions

github-actions Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

Code Intel Quality Signal

Completeness: complete · snapshot 6434d69b54aa · commit 9dbff0267822
Admission: pass · policy evidence-quality-admission v1 · aggregate regression: not_declined (advisory, not a blocking gate)

Total Baseline Delta
6750 6631 [OK] 119

Bottleneck: depth

Root cause Baseline Current Delta
modularity 0.29 n/a
acyclicity 0.0 n/a
depth 8.0 n/a
equality 0.47 n/a
redundancy 0.0 n/a

Findings (1 total)

Kind Severity Disposition Rule Message
root_cause_diagnostic medium advisory depth Quality Signal bottleneck: depth

This branch has not been deployed

No deployments
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.

1 participant