Setting upstream for branch with 2 forward slashes causes git to error

[eksno]

Describe the bug
Creating a branch with 2 forward slashes in the name locally works fine, but when I try to push it it fails to set the upstream. Despite of this it does manage to push the branch to remote before erroring.

To Reproduce
Steps to reproduce the behavior:

1. Create a branch with 2 forwards slashes, for example feature/project/make-a-change
2. Try to push the branch to remote

Expected behavior
The upstream to be set successfully

Screenshots

Version info:
lazygit --version
commit=, build date=, build source=nix, version=0.41.0, os=linux, arch=amd64, git version=2.43.2

[stefanhaller]

This is not a lazygit bug, pushing a branch with two slashes in it works just fine, normally.

In your case, you are trying to push the branch feature/startino/add, but a remote tracking branch feature/startino already exists in your clone. Git doesn't support this (if you had a local branch a/b, you couldn't create a new local branch a/b/c either). It doesn't seem to exist on the remote, otherwise the push wouldn't have succeeded. Either go to your remotes tab and delete that remote branch, or follow the advice that the error message gave you and run git remote prune origin to remove the stale remote tracking branch.

Side note: I recommend to do git config --global fetch.prune true so that stale remote branches are always pruned automatically when you fetch.

[ChrisMcD1]

/close