Repository navigation
feat(host): name a PR workspace's local branch after the PR branch - #7
Merged
Merged
Conversation
Orca names the branch after the workspace title. Rename it to the PR's head ref right after creation; when git refuses (name checked out in another worktree, or already taken), keep Orca's name and warn.
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.
Why
Orca names a new worktree's branch after the workspace title (
<user>/pr-12-fix-login), so a PR workspace's local branch never matched the PR's remote branch.What
git branch -m <head_ref>renames the local branch, before the upstream is set. Orca has no CLI flag for the branch name.Local branch kept as <orca-branch>: <head_ref> already exists. The agent still starts.GitCli.fastForwardand the newrenameBranchshare atolerateRefusalhelper (refusal →false, timeout still throws).(reused)for a new workspace.Known limit: Orca's setup hooks run during
worktree create, so they still see Orca's branch name.Tests
npm test(258 passed),npm run typecheck,npm run build,npm run lint:firefox(0 errors; 2 existing warnings aboutdata_collection_permissions).