Small Fixes
Added 1800 new lines…
Hey, no one ever asked for the quantity of small fixes :3
One senior guy managed to merge with the commit template, as is, with
**Insert brief summary here**
and**description goes here**
189cbca
refactor425b7de
increased bullshitry levels33bc72d
works on my machinef5fe8ed
who the fuck cares112e7ff
probably did more shitc02191c
updater cool factorTwo users trying to chat with each other via commit messages.
1: “Youtube bro” 2: “Ohoo thanks”
It was one with a message that someone copied from a commit I had made a full year before. It broke the build right before a release and the commit message bore no relation to the changes, of course.
Because they had copied my message, it had my initials in. I had visits from irate managers in other buildings who ranted at me for a good 5 minutes without letting me get a word in to tell them that 1) it wasn’t me, and 2) undoing a subversion commit was a one-line command and not a good reason for the stupid amount of drama (there were no database or other irrevocable changes).
The last manager to speak to me told me it was still my fault as it was a bad message in the first place. The message read “Fixing typo in the audit log”.
Debug
Degug
Debugging
Itdiydigxigxjxutxu
Debug
“fix ci” “Again” “Maybe?”
Every time I work on CIs I just lose it after 1 or 2 commits and squash merge later on. Also when integrating projects together (eg I’m working on a language and made a POC for a new parser in a separate project) I’m just like “hajzjgkzlabai yes”
I know I’m having a bad day when my commit messages have question marks in them.
“A dumbass committed her email address hardcoded as a recipient for all mails, again.”
– Me, the dumbass
Worst commit that i pushed receantly was
git commit -m "._."
for my personal js practice repo. I needed it because all of the content is “CRLF” but I’m using “LF” on my machine.For personal stuff especially when I use git just to sync between laptop and computer most of my commits are the things that don’t work and I use for new stuff ~for changes and X for broken stuff.
So a commit can be " + new feature ~logging to accommodate new feature X Edge case crashes the new feature."
I use a single dot when committing to a feature branch. I will either
rebase
ormerge --squash
anyway, so what’s the point really.e: in my private projects that is, I use a jira ticket number at work, because I have to.