Repository navigation
fix(host): start PR agents after branch configuration - #11
Merged
Merged
Conversation
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.
New PR workspaces could start an agent before their local branch was renamed, letting the agent act on the generated branch name.
Create the workspace without an agent, rename the branch, link the PR and configure its upstream/status, then start the agent with the interpolated prompt. Setup scripts continue running in the background. A branch-name collision still produces a warning and starts the agent; Checkout only still starts no agent.
Validation:
npm test(262 tests passed),npm run typecheck,npm run build, andnpm run lint:firefox(0 errors, 0 warnings). Regression coverage checks startup order for Review, Continue work, Address comments, and Custom prompt.