Committing to a new branch to hg repository always commits modified files even when they're not selected

When creating branches, we tend to do an empty commit just to create the branch. However if you have modified files in the working copy when doing so, SourceTree seems to commit those files too even though they're unselected in the commit window.

2 answers

Why do you do that? Try just right-clicking the new branch and pushing it to origin. It won't be displayed as a branch in the graph, but that doesn't mean it isn't one.

This is in Mercurial, not git, so you can't just 'push'. You have to commit to a new branch.

And regardless, if the files are un-checked in the commit window, SourceTree should not commit them, that is a bug.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Oct 23, 2018 in Sourcetree

Tip from the team: configure your repos for hosting goodness!

Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...

1,123 views 4 2
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you