Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,554,529
Community Members
 
Community Events
184
Community Groups

SourceTree commit doesn't do anything

In VSTS I have pulled the master, branched, made a change, staged the change, and clicked Commit and nothing happens.

 

I tried using a repo in GitHub. I pulled the master, made a change, staged the change and clicked Commit... and nothing happens.

What do I have to do to commit a staged file?

4 answers

Same issue. 
I have been using the terminal window to issue the commit.
everything else I can do in source tree. 

Just got Sourcetree on a new laptop and I have the same issue but the terminal has worked to get around this.

1 vote
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.
Nov 15, 2016

Ok, that's very helpful. TL;DR - Looks like a bug.

Firstly, committing NEVER needs credentials. Commit is a local operation - it does not interact with remote repositories. Now, you're using SourceTree, which has a checkbox to automatically Push, which is a remote-interacting operation, so you may get both grouped together (you don't have that box checked though).

When you say you're pushing the commit button, I assume at this point that you are hitting the bottom-right button to try to actually finalize the commit (as opposed to the top-left button, which brings you to the view in the screenshot). Everything in the screenshot looks right and ready to commit. If the Commit, Commit Options.., and Recent Comment (clock) buttons aren't responding, that's got to be a bug. Nothing about the state of your repo should be preventing SourceTree from doing those operations.

You can report the bug to jira.atlassian.com. Hopefully Atlassian staff will be on top of it, and help you find the application logs they need to identify what's going on.

I'm only hosting the Git repo in VSTS. All the actions have been done in SourceTree.

I get the feeling it's asking/waiting for credentials but I can't see any way to get credentials to the app. I tried adding my credentials to the git config but that doesn't change anything.

The "Commit Options..." dropdown and the clock button do the same thing - Just don't respond.

SourceTreeCommit.jpg

 

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.
Nov 15, 2016

Can you upload a screenshot of SourceTree's current state?

Also, why are you pulling, branching and staging in VSTS, but committing in SourceTree?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events