Repository navigation
Conversation
Contributor
Merge Protections🟠 1 of 2 protections blocking · waiting on 🤖 CI
🟠 Queue ready pull requestsWaiting for
Waiting checks:
|
|
[Medium impact] The change affects frontier setup in the orchestrator workflow. Fix the repository-wide PR limit before merging so older stacks remain discoverable. Findings
SummaryReplaces per-branch forge queries with one repository-wide query and batches Git SHA lookups.
Reviews (1) · Last reviewed commit: "perf(orch): collapse frontier set to two..." · Reviewed by Greptile |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #249
What changed
Collapse \orch frontier set\ from 3N + 2 subprocesses down to a flat 4 subprocesses:
Verification
Mergify does not queue a pull request without \live-gate\ on its exact head. Do not merge, tag, release, or roll out without it.