My first big lesson in Labeling Git Commits improperly

I just want to document,

as someone who's in their first years of programming, I feel like this is a mistake I've been anticipating.

Everyone always says to be diligent with your github commits and messaging.

So, I'm working on a project where I am the main programmer. Meaning, I'm the only programmer. 

I've got a git repo, and i have make a commit each time i realize it's been a while since I made a commit, and since this project is a total mess of learning, 

all my commits are completely multi thought, and all of them are titled "wip"

and now i've hit a bug, something that used to work, no longer does, and I can't think of why. and as i comb through my git commits, make a new branch, roll back and don't keep the changes, i can see, that just two weeks ago, the code that now doesn't work, did.

but shit if i know what I changed in a specific way. I mean, i know i did a lot of stuff under the hood to the model objects. and yeah, probably that should have been a commit that is not coupled with all the work i did on the filtering arrays with NSPredicates... 

and i think to myself, if i had just been running simple tests, i might have caught this... but now..

now it's time to unravel.

and it's just a concrete understanding of the ideas of being diligent about your commits... i wonder if it will actually change my behaviour.