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

xyz_st May 1, 2014

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

0 votes
xyz_st May 5, 2014

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.

0 votes
Seth
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 1, 2014

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.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events