this post was submitted on 03 Jul 2023
10 points (100.0% liked)

Git

2882 readers
2 users here now

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

Resources

Rules

  1. Follow programming.dev rules
  2. Be excellent to each other, no hostility towards users for any reason
  3. No spam of tools/companies/advertisements. It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

Git Logo by Jason Long is licensed under the Creative Commons Attribution 3.0 Unported License.

founded 1 year ago
MODERATORS
top 16 comments
sorted by: hot top controversial new old
[–] mertssmnoglu@programming.dev 4 points 1 year ago

Two users trying to chat with each other via commit messages.

1: "Youtube bro" 2: "Ohoo thanks"

[–] theory@programming.dev 2 points 1 year ago

I just pushed "idefk", cause frankly, no idea what was in it, but it touched half the repo

[–] boo@lemmy.one 2 points 1 year ago

One senior guy managed to merge with the commit template, as is, with **Insert brief summary here** and **description goes here**

[–] DoubleEndedIterator@programming.dev 2 points 1 year ago (1 children)

Small Fixes

Added 1800 new lines...

[–] astraeus@programming.dev 1 points 1 year ago

Hey, no one ever asked for the quantity of small fixes :3

[–] SuperFola@programming.dev 2 points 1 year ago (1 children)

"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"

[–] fallenpixel@programming.dev 1 points 1 year ago

I know I'm having a bad day when my commit messages have question marks in them.

[–] verstra@programming.dev 2 points 1 year ago

Empty commit message. Yes it's possible. Yes it's as bad as the cli tries to prevent it

[–] mertssmnoglu@programming.dev 2 points 1 year ago

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.

[–] mostlypixels@programming.dev 1 points 1 year ago* (last edited 1 year ago)

"A dumbass committed her email address hardcoded as a recipient for all mails, again."

-- Me, the dumbass

[–] kabat@programming.dev 1 points 1 year ago* (last edited 1 year ago)

I use a single dot when committing to a feature branch. I will either rebase or merge --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.

[–] MooseBoys@programming.dev 1 points 1 year ago

git commit -m 'oops'

[–] Lunivore@lemmy.world 1 points 1 year ago

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”.

[–] PoolloverNathan@programming.dev 1 points 4 months ago

189cbca refactor

425b7de increased bullshitry levels

33bc72d works on my machine

f5fe8ed who the fuck cares

112e7ff probably did more shit

c02191c updater cool factor

[–] Nomecks@lemmy.ca 1 points 4 months ago

Debug

Degug

Debugging

Itdiydigxigxjxutxu

Debug

[–] blurr11@programming.dev 1 points 1 year ago* (last edited 1 year ago)

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."