It's not a folder that exists, it's a branch. (Well, there may be a folder/directory involved somewhere—or maybe not, as references get "packed" and stop existing as files within directories.)
- If branch
b
exists, no branch named b/anything
can be created.
- Likewise, if branch
dev/b
exists, dev/b/c
cannot be created.
This is a git internal limitation. In this particular case, remote origin
has a branch named dev/sub
(regardless of whether you have it or not, the important thing is whether the remote has it). In order to create, on origin
, a branch named dev/sub/master
, you must first delete the branch named dev/sub
on origin
:
git push origin :dev/sub
(Of course, deleting this branch may delete something important over there, so be sure you know what you are doing. Generally, you might want to git fetch origin
first, capturing their dev/sub
as your origin/dev/sub
. You can then make a local branch named dev/renamed-sub
pointing to the same commit, create dev/renamed-sub
on the remote, delete the remote dev/sub
, and then create dev/sub/master
on the remote.)
If you can log in on the remote (the system that origin
is hosted on), you can go into the repository over there and simply rename the local dev/sub
branch. (Based on comments below, I suspect that there's a broken auto-deploy script over there as well, which probably should be fixed to only deploy "deployable" branches, rather than everything that gets pushed. But I am just guessing here.)
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…