You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
HUB_VERBOSE=1 hub pull-request -p -m "Hub creating a PR to my default branch upstream/core_master"
More info:
$ hub --version
git version 2.21.1
hub version 2.14.1
I've used git remote set-head upstream core_master and git remote set-head origin core_master to set my default branches.
I noticed this issue originally added support for hub creating pull-requests to the defualt base branch when one wasn't specified using the -b flag.
What happened:
When I do hub pull-request from my clone, hub correctly chooses upstream/core_master as my default base branch; however, if I execute the same command in a worktree of this clone, hub defaults to using upstream/master.
csaska
changed the title
Hub doesn't correctly use my default base branch when executing cmd from worktrees
Hub doesn't use my default base branch when executing pull-request cmd from worktrees
Feb 28, 2020
Command attempted:
HUB_VERBOSE=1 hub pull-request -p -m "Hub creating a PR to my default branch upstream/core_master"
More info:
I've used
git remote set-head upstream core_master
andgit remote set-head origin core_master
to set my default branches.I noticed this issue originally added support for hub creating pull-requests to the defualt base branch when one wasn't specified using the
-b
flag.What happened:
When I do
hub pull-request
from my clone, hub correctly chooses upstream/core_master as my default base branch; however, if I execute the same command in a worktree of this clone, hub defaults to using upstream/master.From the worktree, I see the following:
From the original clone, I see the following:
Question:
Is this intended behavior? Is this a bug? Or am I requesting a new feature here?
The text was updated successfully, but these errors were encountered: