How do I ignore a mercurial branch with spaces in it?

Question

I am trying to use hggit to use mercurial as a client for a git repository.

I can't push to the git repository because some genius created a branch called GTS 170528 (note the space).

When pushing from hg to git, I get the error:

dulwich.errors.RefFormatError: refs/heads/GTS 170528

I can only assume that the space is the problem. I am aware that you can't really rename an hg branch.

Any ideas on how to get either Mercurial to ignore it on the outbound, or git not to care about it on the inbound?

That's a bad branch name in Git, too. Get that branch renamed. — jthill, Feb 18 '20 at 19:20
It is [hard but not impossible to rename a Mercurial branch](https://stackoverflow.com/q/4378684/1256452). — torek, Feb 18 '20 at 21:37
@torek -- that doesn't really rename a branch, it merely closes it. Alas. — Nick Hodges, Feb 20 '20 at 13:23
There's an answer in that thread about using the Convert extension, which really can rename branches. — torek, Feb 20 '20 at 17:49

score 0 · Answer 1 · answered Apr 21 '20 at 08:29

the shortest path would be to get the branch renamed in git, in order to have it comply with git-check-ref-format

you can find your very same case reported in dulwich issues, which resulted in a new issue for hggit but the latter won't help your scenario

therefore, as said, get the git branch to comply with check-ref-format

PS: about renaming Mercurial branches, keep in mind that also bookmarks work for hggit sync, not only named branches

Dan Villiom P. Christiansen · Answer 2 · 2021-02-02T06:51:01.837

This is a bug in hg-git, and we just applied a fix for it. You can address this in one of several ways:

Upgrade to hg-git 0.10.0.

Close the offending branch:

 hg update "GTS 170528"
 hg commit -m "close branch with silly name" --close-branch

If it's a bookmark, rename it:

 hg bookmark --rename "GTS 170528" "GTS-170528"

Since Git doesn't actually track branches, but merely has markers pointing to them, simply removing or changing the branch or bookmark should allow the push to succeed. Hence, you won't need to genuinely change the branch of the commits, and just following the advice on how to rename branches will suffice.

How do I ignore a mercurial branch with spaces in it?

2 Answers2