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,362,179
Community Members
 
Community Events
168
Community Groups

Can't click commit button

Hi there,

As of yesterday, I am unable to click the commit button on source tree after I have left my comment and checked off the files I would like to commit. I am on Version 1.8.3. Has something changed or did I need to upgrade?

Thanks,

Rachel 

 

19 answers

I had this problem too. It turned out that my lower-right area is not clickable for any app.

I used process explorer and dragged the "find window's process" thing to that area and it highlighted slack.exe.

I killed all the slack instances and the problem went away, even when I restarted slack.

I'll notify slack.

Same problem here - killing Slack fixed it

Couldn't believe it, but yes, here as well.

Slacked caused this for me as well.

Thanks for sharing this !!

Thank you so much for this!

As of today still a fix for a very annoying issue. I thought I was having a stroke and forgot how to commit for a second...

Slack was causing the issue for me too. 

Yes, same problem caused by Slacked. Cannot close Slack properly, so has to kill it.

I have this same problem. I have found that if you switch to a different tab at the bottom such as Log / History or Search and come back to File Status it will be enabled.

That fixed it for me. Issue still remains in August 2018 in Windows V2.6.10

Thanks, Mike. That's the solution for me as well.

Like Chris Needham likes this

I ran into this issue today for the first time on windows version 2.6.10.0. I tried closing SourceTree, switching tabs, re-staging files, nothing worked.

I ended up resizing the window and the button started working right away.

I checked out WebStorm and had the same issue. I couldn't close a notification window that was up.

So, then I tried file explorer at maximum size. Couldn't press any buttons that were in the bottom right corner of the screen. That means, at least in my case, this isn't a SourceTree, nor Atlassian specific issue.

There must be some notification in Windows that it thinks it's displaying and therefore disabling input at that specific spot on the screen.

Same for me. I can't click the commit button at the moment on my primary monitor when source tree is full screen. If I make it smaller, or move it to full screen on my secondary monitor, it works fine.

Also confirmed that it affects other programs too, so it's Windows, not a SourceTree issue (in my case anyway).

are you running slack? see my post below.

Ah, thanks Ken. Yes I am. I'll do the same check you did next time it happens to confirm that it's Slack. Thanks!

Same problem after upgrading to 2.10.0 on Windows. Solved by unstaging, and restaging files multiple times.

Same, also closing and opening Sourcetree several times or performing several fetchs can shake it loose if the staging/unstaging doesn't do it.

Like Chris Needham likes this

This issue still remains. Button is not greyed out, but does nothing when clicked.

in my case I wanted to pull but had to commit before..
It says I have local changes in commit but I couldn't see it plus I had nothing important, so I pressed 'discard', and discard all changes. the commit disapeared, and I could pull :)

Amazing, almost four years since the original post, and this just happened to me. Closing Slack fixed it. Bizarre!

I also faced same issue. Best way to resolve--In commit option select any of the option, commit button will get enabled and later, make commit option as is -means drop down selected to -:Select commit option" and this works, you will have commit button enabled.

Sorry.. wrong post just now..

Getting this happening on 3.0.12.

 

Commit button in bottom-right corner works fine.

 

Big commit button in top-left corner doesn't work. Was quite embarrassing during our Git workshop as it's one of the most basic operations!

 

Our project has lots of submodules.

Solution? A long merge conflict log is blocking the screen. Just delete the '#' lines to make the commit message smaller, then the buttons reapear.

A potential easy solution: try clicking slower.

On my (Windows) machine clicking the "Commit" button with a normal mouse-click works maybe 25% of the time. But when I click and hold the mouse button--even for just a quarter of a second--before releasing, the "Commit" button works 100% of the time.

Does this work for anyone else?

I had the same problem but I think it was my error because I had to select the files I wanted to commit and click first on "Stage selected" (or press "Stage all"). Then the files with changes were ready to commit and button appeared enabled.

In mac I don't need to do this step.

I had this issue, but it was a non-issue, I just had to select all files to commit, if not, the commit button is grey. Hope it helps someone. :)

I am still having this issue on 2.3.1.0 and it has been this way since I upgraded from 1.5.2 about a year ago. The only thing that seems to fix it is closing sourcetree waiting for a couple of minutes and then reopening it and then typing in your commit message again. Then it works properly for awhile. Another thing I have noticed when I have this issue. I can click on commit multiple times and it doesn't work, but then I hit the enter key (not the numpad side enter key, the main one) and then it commits sometimes even though clicking the button didn't work. 

Side Note (maybe related): Sometimes when I go to open a repo I have. I cannot open the repo and the open is greyed out. Then I do the close sourcetree/ wait 2 minutes / reopen and I can open the repo then.  It might be something do with one of the file watching threads getting stuck in the background for that specific repo and locking up the tab if the tabs are all on separate threads, which they seem to be. Just my two cents.. Hopefully this gets fixed soon though. I am about to go back to 1.5.2 because the newer version has a bunch of issues.. especially with it noticing the working copy changes. Sometimes I have to wait for like 5 minutes or close and reopen just for it to see the working copy changes :/ but of course that could go into a trouble ticket also. 1.5.2 was awesome btw.. best version ever :] 

I've had some success running clean up on the local repository. As on a windows machine had gitui installed, which will prompt to clean up the repo when you open it. Did help.

I moved on to a different tool awhile back.  Every now an then I confirm it's still broken, because I do like SourceTree on the Mac.

It's hard to believe that the primary functionality of the Windows version of this product has remained broken for over 4 months now.

I suppose very few developers use Windows + SourceTree.

I was thinking that Im making something wrong. 

Ok command line here I go!!!!!!!!!!!!!!!!!

Works fine on Mac but still broken on Windows.  Rebooting no longer fixes it after today's SourceTree update.  Task Manager shows SourceTree using 10% CPU and 300MB to 500MB RAM while just sitting idle.  Must be other major problems with this app.

I haven't seen this problem since updating to version 2.x.  Just installed the 2.1.10 update today so no commits yet. 

Note: The STSP-4428 issue referenced above has been Resolved.  Someone should open another, or reopen 4428, if not already done.

Half a year later, the issue still exists.. Is it going to be fixed anyday?

Yes - still an issue for me too. My user a/c on my Windows 10 computer doesn't have admin rights. I wonder if this is something to do with it.

I found out "staging" the edited files allowed me to commit the changes. 

 

Try it to see if it works :)

2019, solution was to stage files :P

Like Jamie Miller likes this

I have the same problem. Tab switching doesn't help either, only reboot does.

Restarted the machine when I left for the day.  Seems to be working today.

Same here.  I am unable to commit any changes via SourceTree.    The Commit, Cancel, and Commit options buttons are all inoperative.  

Version 1.8.3.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events