Why can't I push this change to my 'main' mercurial repository?

mercurial branch tortoisehg
Neil Trodden picture Neil Trodden · Mar 2, 2010 · Viewed 18.3k times · Source

I am trying to grok Mercurial and hope I am just getting confused here!

I have a repository ('main') that I have cloned ('clone'), , both on my own machine. Both were completely in sync with each other.

I decided to play with named branches so the next time I committed on my 'clone' I did it under a branch name of 'case1212' and while it seems to have dealt with the commit properly on my clone, I cannot push these changes back to 'main'. The error given is:

abort: push creates new remote branch 'case1212'!

...and it suggests that I might need to merge first? What am I supposed to merge on that 'clone' repository? When I try to pull from 'main', there are no changes.

I'm pretty sure I actually would want it to create a remote branch in my 'main' repository so people who update from it can see that branch.

Answer

Nate Heinrich picture Nate Heinrich · Mar 2, 2010

Mercurial's default behavior prevents you from creating remote branches. If you want to do this, you need to force-push.

Synchronize menu in the window you show, there is an option for force push.

Related questions

Mercurial — revert back to old version and continue from there

I'm using Mercurial locally for a project (it's the only repo there's no pushing/pulling to/from anywhere else). To date it's got a linear history. However, the current thing I'm working on I've now realized is a terrible approach …

Read More
How to correctly close a feature branch in Mercurial?

I've finished working on a feature branch feature-x. I want to merge results back to the default branch and close feature-x in order to get rid of it in the output of hg branches. I came up with the following …

Read More
Mercurial: Can I rename a branch?

We now have a "stiging" branch, where "staging" seems to be a far better semantic fit. What's a good strategy for handling this?

Read More