When you stare into git, git stares back.

It's fucking infinite.

Me 2 years ago:
"uh was it git fetch or git pull?"

Me 1 year ago:
"Look, I printed these 5 git commands on a laptop sticker, this is all I need for my workflow! branch, pull, commit, merge, push! Git is easy!"

Me now:
"Hold my beer, I'll just do git format-patch -k --stdout HEAD..feature -- script.js | git am -3 -k to steal that file from your branch, then git rebase master && git rebase -i HEAD~$(git rev-list --count master..HEAD) to clean up the commit messages, and a git branch --merged | grep -v "\*" | xargs -n 1 git branch -d to clean up the branches, oh lets see how many words you've added with git diff --word-diff=porcelain | grep -e '^+[^+]' | wc -w, hmm maybe I should alias some of this stuff..."

Do you have any git tricks/favorites which you use so often that you've aliased them?

Roughly 180 days, 5 months and 29 days, 4,320 hours, 259,200 minutes, I devoted myself to a client project. I missed family outings with my daughter and my wife. People started asking my wife if we had broken up. My daughter became accustomed to daddy not being around and playing with her. Sometimes only sleeping 4 hours, I would figure out solutions to problems in my sleep and force myself to wake and put them into action. My relationship with my wife became very fragile and unstable. I knew I had to change but I just needed a little bit more time to complete this client project.

Finally, the project was ending there was light at the end of the tunnel. I “git add –-all && git status” everything looked good. I then “git commit -m “v1.0 release candidate && git push beanstalk master”

I deployed the app to the staging server where I performed my deployment steps. Everything was good. I signed-up as a new user, I upload a bunch different files types with different sizes, completed my profile and logged out. I emailed the client to arrange a time to speak remotely.

“Hello” says the client “How are you” I replied. “Great, lets begin” urged the client. I recited the apps url out to the client. The client creates a new account and tries to upload a file. The app spews a bunch of error messages on the screen.

The client says

“Merlin – I do not think you really applied yourself to this project. The first test we do and it fails. If you do not have the time to do my project properly please just say so now, so I can find somebody else who can”

I FREAKED THE FUCKOUT on the client!!!!!!! and nearly hung up. My wife was right next to and she was absolutely gobsmacked. I sat back and thought to myself “These fuckers don’t get it”. All that suffering for nothing!

Thanks for reading my rant….

BTW: I did finish the project, the client was amazed on how the app worked and it is has become an indispensable tool for their employees.

A new way of making bad commits:
alias fuckit='git commit -m "$(curl -s whatthecommit.com/index.txt)"'

Its like Russian roulette with commit messages!

This guy is clearly not having the best Friday 😂😂

With the other members of the team refusing to learn git and making changes directly to the staging server i get to write the commit messages for everyone.

Log:
UPDATE: *informative details *

UPDATE: mark made some changes

UPDATE: colin made the same changes as mark but different

UPDATE: andrew undid all colins updates to change one link and I had to add them back in, thank gawd I commit the night before

BUGFIX: andrew keeps changing the database host to localhost and uploading it without changing it back

UPDATE: we all hate andrew

Me af.

I generally like to separate changes into as many commits as is reasonable. That way I can go back and see how, why, when and what was changed, along with meaningful commit messages.

But sometimes...
Git add *
Git commit -m "changed lots of stuff"

God I hate myself.

Watch your git commit messages, you never konw when a webhook might publish the whole thing to Slack...

Made poor commit messages for a repo and then found out that we were going to start doing peer reviews at school the next day and that we were going to be assessed by git commit messages.

Rebased at 2 in the morning. Rewrote every commit message.

Did not get assessed by git message.

WTF is up with open-source projects using emojis in their commit messages... FUCKING emojis..

I get it, programming is fun and a hobby to many, but can we also keep at least a minimum level of professionalism here.

WTF is a wheelchair or bento emoji at the beginning of a commit message supposed to mean? Why the hell even bother to use it in the first place? There is no fucking reason for this retarded shit.

Is this what happens when activist developers get out of their way to make programming "inclusive"?

It is your personal project and so if you want to use emojis it is OK, I respect that (not really) but I can't trust your code, your commitment, or the quality of your work if I see those dumb Unicode characters there.

Git commit messages are not a game. Be playful with comments in code or your readme.md file but git messages should be a clear reflection of the changes not what a teenager's phone vomited on the keyboard.

My favorite git commit messages:
- "Changed Something"
- "Fixing Something"
- "asda"

git blame

More like
git whose line is it anyway

Where commit messages are made up and the branches don't matter

whenever my team starts on a new project we're all like "okay we're gonna have MEANINGFUL commit messages this time guys"

*5 hours later*

$ git commit -m "go fuck yourself"
[master a7b9de] go fuck yourself
1 file changed, 1 insertion(+), 0 deletions(-)

The effort I put into git commit messages directly reflects my mood and level of tiredness.

You know you fucked up when you had to commit with the message "I'm sorry"

Ok interns , enough with this sh!t.

Commit Message Part2:
6528fff Code was clean until manager requested to fuck it up
241b35f Who knows WTF?!
4381a32 Argh! About to give up :(
c3bf1a9 more debug... who overwrote!
2d68d6d Fixed a bug cause Maciej said to
b112c1a This branch is so dirty, even your mom can't clean it.
bb456d4 Shit code!
4878b46 Copy-paste to fix previous copy-paste
e2c7e87 A fix I believe, not like I tested or anything
f56109f derpherp
e4b8f4c formatted all
3691208 I'm just a grunt. Don't blame me for this awful PoS.
0888b69 just checking if git is working properly...
62741aa I'm too old for this shit!
0735196 COMMIT ALL THE FILES!
09caccf I CAN HAZ PYTHON, I CAN HAZ INDENTS
1e1cda8 giggle.
ab70bde Fixed errors
934436d Now added delete for real
5f84e30 My bad
99baff8 CHRIS, WE WENT OVER THIS. C++ IO SUCKS.
953473d final commit.
f0c3b57 Just committing so I can go home
4e5ce4e yolo push
deb4e3b I CAN HAZ PYTHON, I CAN HAZ INDENTS
710c06a Commit committed....
3c45e67 it is hump day _^_
4487788 Committing in accordance with the prophecy.
bf86e7e This solves it.
4804f68 FONDLED THE CODE
051d42e REALLY FUCKING FIXED

No, "Remove big elephant" is not a suitable commit message. Especially not 15 times in a row 😒

Beginning of the project:
git commit -m "Added index.html, implemented user-creation"

Towards the end of the project:
git commit -m "Idunno, did some stuff or so (ノಠ益ಠ)ノ彡┻━┻"

Well there were quite some teamwork fails concerning Git and build environments. I covered a few in my previous rants.

Basically I become a tiny bit of FUCKING ANGRY when I have to work with lobotomized pricks who get a segfault at address 0x00000000 in their brain_x68.exe when it comes to handle Git in the simplest ways possible.

Horrible commit messages, unfinished/buggy stuff pushed to master, force-push with fucking 6 months old code +1 change, pushing "resolved" mergeconflicts without resolving, 1 year old issues which are not closed or marked in any commit message, copying repofiles into a backup folder and committing it, not commiting files and change it directly on the FTP...
I HAVE SEEN IT ALL.

If I was not a calm and thoughtful guy I have had exploded and quit a long time ago!
I only help them so they can improve their dev style and workflows.

Amending ancient Git commit messages because there's a typo and then force pushing

RIP everyone else working on the same project

git commit messages

at work:
Only related changes on commit
"Detailed explanation of changes
- This bug
- That bug"

personal project:
1732 changed files
"Changes"

I'm not sure if diamonds are forever, but Git commit messages after you push, sure as hell are.

git commit -m "I hate bad commit messages"

Used a starter to scaffold a new project. Have never used that starter before but it has more than 1400 starts on Github.

Two days after.... so far so good. The created project structure used some tools I haven't used before, some are good, others are not so good, but anyway I am towards the first release of my codes. I have done countless 'npm run build', 'npm run test', 'npm run fix', etc., but.... my fault, I haven't committed once since starting the project, thinking I would commit when the next function is implemented, next test case passed.... after all, what could go wrong anyway?

Finally, one last test case passed, I think I will commit and run 'npm publish'.... but wait, had a glimpse of the scripts section in package.json, there's a command named 'all'. An voice came out of nowhere was talking to my subconscious mind, "all.... build, lint, prettier, test..... yeah you should run all... it's another build script, the worst you can get is just some harmless error messages.....", and my fingers typed 'npm run all'...

Time stopped for a few seconds, file structure in project explorer was shifting, files & folders were disappearing & appearing, what's happening... and I looked at the 'all' script closely for the first time....

WHAT THE HELL, WHO SHOULD PUT 'git reset --hard' IN A BUILD SCRIPT WITHOUT ANY PROMPT????!!!!!!!

MY PLAN WAS TO COMMIT AND GO TO SLEEP, IT'S 1AM NOW!!! WHERE CAN I RECOVER THE LOST FILES????

I started my actual gig as CTO of construction group (Innovation Hub) a year ago. And it was a hell of a ride, implementing kind of a scrum-ban for project management, XP, peer-reviews, a git-flow, git commit message formats, linters, unit testing, integration tests, etc...
And it's the fun part because with the CIO we had to drive the board to do A LOT of changes in their IT/Innovation drive.

But in one year there is a lot of KPI that went up :
* Deployment: When I arrived it took three stressful days to deploy a new version of one application, once a month. Today we do it every week, and it takes three annoying hours.
* We had no test. NOTHING! Today we have 85% code coverage for the unit test, and automatic integration tests run by our CI server every day.
* We had almost no documentation. Today our code is our documentation (it automatically extracted and versioned).
* We had 0 add value in the use of git. With commit messages as "dev", "asked task", inside jokes and a lot of "fix" and "changes". Today we have a useful git, and we even use it to create our deploy changelogs (and it's only mildly annoying!).
* More important, the team is happy! They get their purpose, see betterment in their tech mastery. They started doing conception, applicative architecture, presentations, having fun.

There is still a LOT of bad things we are still working on, and trying to solve (support workflow and betterment). But seeing what they already did, I'm so proud of my TEAM! I'm a fucking asshole, workaholic, "just do it" kind of guy. But they managed to achieve so much. Fucking PROUD!!

Drinking game:
Everytime you see a typo in the commit message, take a shot.

I know it's not recommended to write git commit messages in past tense, but it makes more sense to me to use it. Maybe I'll change as I grow and learn more in the programmer world, but as for now, I'm going to be a rebel and ignore convention😎

WTF PEOPLE!!
Some people really need to read their error messages.

Just now I got this teammate asking me how he should handle the error git returned. The error message stated: "Please commit your changes or stash them before you merge." He asked me what he should do to fix the error... I was astonished by his stupidity that he did not read the fucking error message.

Almost every fucking time a teammate comes to me with the question how to fix an error, there is a message that says how to fix the error. Why don't they read them?!?! I told you so many times to read your fucking error messages!!!

I'm really glad the project is over in a couple of weeks and I get a new team..

I really don't mind it as long as the work is on track but damn it hurts to read the git commit messages with messed up spellings. In some cases it's not just that, but variable names, file names, etc. as well.

English isn't the first language in my country and a lot of people are not as proficient with it so it's probably not appropriate to judge, but the cringe is real.

Sometimes I wonder if I am that cringeworthy person to someone else.

My new team mates type in the date and time of commit on their commit messages and maintain code only on master branch. Some people deserve have their write access revoked.

Best git commit messages ever(sarcasm):
- Fixes.
- Changes.
😥

Just spend 7 hours till 2:30 fixing a minor bug.... Disappearing messages... Git commit? 20 lines...

Test1, t2, 3...

So someone complained to my bosses boss about some internal page where I collected some of our own funny git commit messages, because they were not "meaningful", and I had to take down said page.

Fuck that narrow-minded seriousness, why be so German? If we have to debug multi-threaded C++ programs, we need that bit of fun and sarcasm to stay sane. But probably that someone is a member of some of these "professional" Agile teams that waste a day a week with fucking retros, sprint planning or other mind-crippling meta stuff, then evaluating frameworks and tools, while we are doing motherfucking programing.

Those people who don’t even understand the commit message

Who commits using commit message “commiting”?

You know what I hate? Git commit messages stating 'fixed tests' or 'fixed docs' or 'fixed integration problems'. You did not fix anything, fuckhead. You updated the code, introducing more bugs as usual. FIXED?! NO, UPDATED! That's what I hate.

Questions/best practises for git?

For example:
- use present tense in commit messages. (why though?)

A friend of mine also starts his commit messages with either [Task] or [Cleanup]. Useful for finding Commits in Gitlab etc, because only the first line is shown from the message.

Also, one teacher recommended the usage of branches and the other didn't because of alot of potential merge conflicts when working in a Team or a larger Collaboration. What are your thoughts?

Sorry for the messy post, have a hangover

I invited a colleague to the repository and taught her some basic git so she could edit some texts without having to interrupt my workflow.

All of a sudden, some parts stopped working. Guess i should have been a bit more articulate when telling her about commit messages..

> merging feature 20155
> Removing debug messages for previous commit
> Fixing bug from feature merge
> Fixing bug from previous fix
> Merge fml

I'm slowly realizing how much goofy code I put in my branch and overlooked. This code review is going to be interesting...

Some examples:

import plots as lel
<h4 id="title">Crunchatize Me, Captain! </h4>
go.Scattergeo(name="cheese", ...)
webster = { ... }

The commit messages are even worse.

- 'horizontalize' link list
- very messily hack in <feature>
- partially refactor some of the awful code from previous
- Remove one annoying space
- make background color less annoying
- remove seemingly useless property
- minor fix
- Apparently it's possible to center a DIV. Who knew?
- Made some cool bar graphs
And then there's just a bunch of reverts.

People in companies who make bad git commit messages beacuse they do not care... Hey, "change 1", "update" makes so much sense. And companies who do not care to have some guidelines.

Started new internship last week, hired as dev but working qa till their next release goes up. See last 3 posts for some horror lmao. They... don't know how to use git but insist they do. 275MB single repo for entire angular frontend (no dependencies are pushed, few images) and "angular backend" (according to PM). Commits to master, bad commit messages, no testing except me on qa..... death

You know what really grinds my gear?
.
.
.
Commit messages like this

I hate it when colleagues name their commits with a non descriptive name like "minor changes", "minor fixes", "small changes" and so on. I know that good naming is a difficult task in software development, but do I expect to much when I want them to explain shortly what exactly they changed since the last commit?
Good commit messages are always helpful if you want to do good PR reviews and furthermore if you want to go back to an older commit because someone fucked something up.
Don't get me wrong, my colleagues are great people and great developers, but some of them ignore the fact that good commit messages might be useful in the future for others and themselves

Since we are sharing some of our more interesting commits, what do people think of these commits?

General: pro.user update
297af8f

Refactor: Hide and show Spin Boxes on Normalization
6a4e1f3

Refactor: Dynamic resizing refactoring
964f0ae

Refactor: Dynamic resizing across any screen
5890a35

GUI: Measure screen size and assume the proper size.
13f2cb4

Fix: guitest.cpp has been reafactored
5cbc1b4

Dir: Clean unused directory
32c8384

GUI: Hide and show Spin Boxes on Normalization
84db444
Commits on Jun 28, 2016

GUI: Make boxes more bolded
3d23952

General Commit: 11:03 PM 6/28/2016
678c249

Del: build from previous commit
e428041

Fix: Guitest's compiled code was broken
25f546f

GUI: Make window scrollable.
07091fd

Adjust; Changing directory tree

Some days I fear I'm the most incompetent. But as someone else made the comment... There are git logs with useless commit messages...