You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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):
TL;DR - reclone your repo from scratch.
Ok I have an actual answer for this one. It was an unknown repo issue for me. Here's what I did to determine that:
1. Wiped all Sourcetree settings, and tried the same thing again - same problem happened.
2. Restored all Sourcetree settings: tried the same thing with a new test repo - could not reproduce the problem.
3. Blew away and recloned my local repo - problem went away.