Not sure if I am missing a setting or if this is a legitimate bug. Whenever I commit, it also commits my unstaged files/hunks. This is obviously very frustrating and has caused some code to be committed that I was not ready to commit or ever intended to be committed. I have included some screenshots to illustrate a simple scenario. Below I only intend to commit the changes for the one file 'environment.dev.ts'. As you can see I left the 2 other files unstaged as I do not intend to commit those changes quite yet. However, after committing the changes I pulled up the commit which shows that all 3 files were committed up anyways.
Before Commit (Staging):
A vulnerability has been published today in regards to Sourcetree for Windows. The goal of this article is to give you a summary of information we have gathered from Atlassian Community as a st...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event