Re: Bug report

From: brian m. carlson <sandals@crustytoothpaste.net>
Date: Jul 19, 2024, 20:13 UTC
Message-ID: <ZprI_wP1km8eA7HA@tapette.crustytoothpaste.net>
In-Reply-To: <CAKexjB-+6VXE8YXrc1YaOVE6bKs05Ty4XHMSBPRHUcUrxpp31w@mail.gmail.com>

Hey,

On 2024-07-19 at 18:34:29, Roman Dvoskin wrote:

Show 12 quoted lines

> 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