Hi Brian,
Yes, you're exactly right, I renamed the branch called PLT-51 to
PLT-50-2 via `git branch -m PLT-50-2`. I may have pushed while on
PLT-51 (and perhaps that's when I noticed that I mis-named the branch)
but I did not create a PR). Then, I renamed the branch to PLT-50-2 and
expected the rest of the flow to continue using the new branch name.
rdvoskin@MT-24 platform % git push
fatal: The upstream branch of your current branch does not match
the name of your current branch. To push to the upstream branch
on the remote, use
git push origin HEAD:PLT-51
To push to the branch of the same name on the remote, use
git push origin HEAD
To avoid automatically configuring an upstream branch when its name
won't match the local branch, see option 'simple' of branch.autoSetupMerge
in 'git help config'.
rdvoskin@MT-24 platform % git push origin HEAD
Enumerating objects: 27, done.
Counting objects: 100% (27/27), done.
Delta compression using up to 16 threads
Compressing objects: 100% (14/14), done.
Writing objects: 100% (14/14), 2.91 KiB | 993.00 KiB/s, done.
Total 14 (delta 12), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (12/12), completed with 12 local objects.
To github.com:MyTechnologiesOrg/platform.git
9b7fc2a..b66bee8 HEAD -> PLT-50-2
rdvoskin@MT-24 platform % git config --global push.default
simple
On Fri, Jul 19, 2024 at 4:13 PM brian m. carlson
<sandals@xxxxxxxxxxxxxxxxxxxx> wrote:
>
> Hey,
>
> On 2024-07-19 at 18:34:29, Roman Dvoskin wrote:
> > Thank you for filling out a Git bug report!
> > Please answer the following questions to help us understand your issue.
> >
> > What did you do before the bug happened? (Steps to reproduce your issue)
> > I renamed an existing branch to a new name
> > What did you expect to happen? (Expected behavior)
> > When I git push I expected the new name to be used to match the remote branch
> > What happened instead? (Actual behavior)
> > I was prompted to use git push HEAD:<old_branch_name>
> > What's different between what you expected and what actually happened?
> > I expected for the new branch name to be used, as if it was always the branch name
> > Anything else you want to add:
>
> I'm not sure I understand exactly the message that you saw here, and I
> suspect if I don't understand, it's possible other people on the list
> don't either. Could you copy and paste the exact output you saw here so
> that we can see what the prompt looks like and the exact response you
> saw? That would help us understand whether the behaviour you saw is a
> bug or not, or if perhaps maybe the documentation is unclear.
>
> Also, to be sure I understand, you did something like this:
>
> ----
> git branch -m foo bar
> git push origin bar
> ----
>
> and you expected the local branch `bar` to be pushed to the remote branch
> `bar`, correct?
> --
> brian m. carlson (they/them or he/him)
> Toronto, Ontario, CA
