Sometimes sourcetree visually indicates that I have commits to push, but, I have no commits since my last pull. Does pull-ing cause this? Is this a bug in sourcetree? The git command line tools do not indicate I have anything to push.
If you had commits that needed pushed before you pulled, they will still need pushed after. Additionally, if the pull created a merge commit, that will need pushed as well. If both situations apply, only one push is needed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you could get a screenshot, that'd be helpful. Pulling shouldn't cause SourceTree to think you need to push, unless you committed before the pull, and the pull resulted in a merge or rebase.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.