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.
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.