With the new version of SourceTree (1.9.0), I am getting commit errors that I was not seeing before.
The main one is trying to Commit changes brought to a branch from a Merge. the local repo contains other changed files that I do not want to associate with the commit (basically, I only want to commit the files that were changed from the merge, and leave the other files out of the commit). It used to be possible prior to 1.9.0. 1.9.0 broke that option.
It is generally advisable to keep settings files out of the repository (they can be in the working directory, but ignored). If you have them in the repo for documentation purposes, I recommend putting them in with an extra piece in the filename.
For example, if your settings are in 'settings.ini', rename the settings.ini in the repo to settings.default.ini, then make it part of standard deployment steps to copy that file to 'settings.ini', then modify it. If this occurs in a repository working copy, the 'settings.ini' file can be safely ignored.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Supported Platforms macOS Windows To make using Sourcetree as simple yet powerful as possible we embed (bundle) dependencies such as Git, Git LFS, and Mercurial. We strive to keep these...
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!
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