Support non-default base branches for agent PRs (evaluation lanes) - #83
Merged
Merged
Conversation
Agent bootstrap PRs always targeted the repository default branch: the issue bridge hardcoded `base = data.default_branch` with no override. That makes per-agent evaluation lanes (eval/claude, eval/codex) impossible — every agent PR lands on main. - reusable-agents-issue-bridge: resolve the PR base as base_branch input > `<!-- base-branch: X -->` issue marker > repo default, with an existence guard that falls back to the default when a marker names a missing branch (a typo can no longer wedge dispatch). The input is passed via env, not inline interpolation. - agents-verify-to-new-pr: carry a non-default PR base into the generated follow-up issue as a base-branch marker (both the LLM and fallback paths), so remediation PRs stay in the lane instead of escaping to main. Resolution order verified against all four cases; workflow YAML validator passes. Two pre-existing long-line lint failures in the bridge are upstream and untouched.
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
2 participants
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.
Agent bootstrap PRs always targeted the repository default branch: the issue bridge hardcoded
base = data.default_branchwith no override. That makes per-agent evaluation lanes (eval/claude, eval/codex) impossible — every agent PR lands on main.<!-- base-branch: X -->issue marker > repo default, with an existence guard that falls back to the default when a marker names a missing branch (a typo can no longer wedge dispatch). The input is passed via env, not inline interpolation.Resolution order verified against all four cases; workflow YAML validator passes. Two pre-existing long-line lint failures in the bridge are upstream and untouched.
Workflow Source
Started from:
Automation intent:
Notes:
Summary
Testing