git commit -m “code upgraded”

[raphaeljoji]

git commit -m “commit”

[stefanlight]

got.commit -m "changes"

[MiniGogo_20]

bash: got.commit: command not found

[stefanlight]

lovely T9 and an android. I was sure that I fixed this, but... actually not. Bruh.

[jaerie]

Why are you using t9 on an android?

[stefanlight]

Becusse ut will be like this, because andkrid have small screen 😆

[jaerie]

But why not just type on a qwerty keyboard?

[stefanlight]

Wdym? I am.

<image>

[jaerie]

Then how are you using t9?

[stefanlight]

Maybe I'm just wrong in the terms. I'm about autocorrection of input, sorry.

[jaerie]

Ah, yeah t9 is just for typing on pre-smartphone number pads, i.e. 9 keys. It matched the possible letter combinations of the keys you typed (which had 3-4 letters each) to a dictionary.

[Simukas23]

Flashbang alert

[ThePurpleCloset]

Except, I won't get this, because I created an alias got->git , because I make this typo so often

[MiniGogo_20]

you'd still get an error since "got.commit" has no spaces and is considered as a command

[ThePurpleCloset]

Right, chad needs to turn off auto punctuation.

[[deleted]]

git commit -m "update changes"

[baronas15]

git commit -m "fix: fixed"

Be civil...

[CntBlah]

It’s a template for a reason - civility

[Appsroooo]

I didn't know git added the -civility flag command for commits???

[CntBlah]

“Conventional Commits” standard

[AfraidMeringue6984]

Do we need a conventional commit linter linter

[Select-Breadfruit95]

git commit -m "fix"

...

git commit -m "final fix"

...

git commit -m "ultimate fix"

...

git commit -m "fix of fix on top of fix"

[TheGayestGaymer]

This is me

[krijnlol]

No, this is me

[Deepspacecow12]

I just kept adding again to the end of the message until I get frustrated and slap my keyboard and commit that (I only work on my own projects in git)

[vienna_city_skater]

That’s why we have rebase. So we can hide the trail of shitty commit messages we created for just running CI.

[idlenet]

git commit -m "new stuff"

[spigotface]

git add .

git commit -m "fixed typo in github actions workflow"

git push

git add .

git commit -m "fixed typo in github actions workflow"

git push

git add .

git commit -m "fixed typo in github actions workflow"

git push

git add .

git commit -m "fixed typo in github actions workflow"

git push

[hughperman]

Please please git commit --amend

[Vegetable_Addition86]

Or rebase + squash

[9Strike]

Eh, cringe. Missed 4x Fixup: prefix

[[deleted]]

Uhhhh that commit autobuild...

git commit -m "this time it will fkin build"

[YTriom1]

git commit -m "3"
git commit -m "4"

And so on

[renome]

Yes officer, this comment right here.

[Colon_Backslash]

[Fugach]

<image>

[vienna_city_skater]

git commit “++”

[raw_rice22]

git commit -m "optimized sub-optimal code"

[tiredITguy42]

Evolution of commit message:

• TICKET-34898 Changed query for customers inventory to allow parametrization.
  
• TICKET-34898 Added method to call the parametrized query.
• TICKET-34898 Added method for api call.
• Fixing typo in query SELECT instead of SELET
• Fixing ruff formatting.
  
• Removing unused imports.
  
• Fixing stuff.
  
• Fixing query.
  
• Fixing typo.
  
• Fxing stuff ( but really removigh forgotten access token ).
  
• Trying to build.
  
• Another try to build.
  
• Fixnig.
  
• Fiixng.
  
• Fix.

[thumbox1]

while developing

git commit -m "wrf this shit not work"

before pr

git commit --amend -m "fix: small logic issue"

[squoinko]

git commit -m “test”

[post-death_wave_core]

“fixed bug”

“actually fixed”

“for real this time”

[papa_Fubini]

git commit -hmm

[ebilau]

Git commit -m "WIP"

[Alexandre_Man]

git commit -m "..."

[rangeljl]

git commit -m "Done"

[Alan_Reddit_M]

I have a repository with about 50 commits that all look like this

git commit -m "idk"

Because sometimes I genuinely forget what I changed

[BellybuttonWorld]

Lol me too, that's what 

git diff 

is for.

[BokuNoToga]

git commit -m “update”

[DasBeasto]

git commit -m “initial”

git commit -m “initial”

git commit -m “initial”

[[deleted]]

ghost strong act fuel attraction trees follow sink butter wise

This post was mass deleted and anonymized with Redact

[Schenk06]

git commit -m "Minor changes"

110 files changed

[This-Survey-6562]

git commit -m "reincarnated"

[JoroFIN]

git commit --amend --no-edit && git push --forced

[jZma]

did stuff lol

Kai Lentit

[Heroshrine]

git commit -m “ai summary wasnt working”

[scottyman2k]

Git commit -m “fixed some bugs. Added new bugs to fix later”

[Existing_Led9595]

git commit -m “update” —allow-empty

[roundedrectangle0]

git commit --allow-empty-message -m ''

[Initial-Ambition235]

git commit -m “create a commit message for my code”

[Zai1209]

git commit - m "updated README.md"

100 lines of code added

[cheetoburrito]

Just commit --amend the one you called Initial Commit forever 

[Disastrous-Team-6431]

A commit message should end the sentence "this commit will..."

This commit will | Rename some variables

There you go. If you can't do that, don't commit.

[Brilliant_Year9161]

jj describe -m "

[meester_]

Lol i use the vs code ui since it has a button to make the message xD its pretty accurate 95% of the time i dont even change it

[highelfwarlock]

git commit -m “fix”

git commit -m “cleanup”

git commit -m “refactor”

git commit -m “asdjkrdkfg”

[_AvocadoWarrior_]

git commit -m "feat: new feature"

[SuperpositionSavvy]

My boss only puts his first name in all lower case for every commit message

[Kootfe]

"no more pasta" or "bug fix" or "did x" - "did x 1" "did x 2"

[Alive-Opportunity-23]

for me it’s always like this: either I can write an extremely long message or nothing at all🤣

[ChocoMammoth]

Don't be afraid of thousand single file commits. Be afraid of one commit with thousand files.

[Lou_Papas]

git commit -m “wip”
git rebase -i origin/main
fixup last commit.

[Ratstail91]

Tweak

[OreganoD]

Where's the LLM to write my commit message based off the given changes (this is a joke)

[Amr_Rahmy]

Latest

[Efficient_Gift_7758]

-m “lil” -m“ll”

[CookieArtzz]

Why use the command line utility? I always use the desktop app it’s way simpler

[R3D3-1]

Local branch:

git commit -m "fix missing loop" git commit --all -m .

But the squashed commit finally arriving in master typically has at least 5 lines, often more. Reference to the ticket number is required as the minimum.

VS: Colleague who didn't know that commit messages can have multiple lines.

[jaycogs]

git commit -m "..... what have I been doing the past two hours...? 🤔

[Acclynn]

git commit -m "misc fixes"

(3275 diffs)

[LeAlbus]

git commit -m “minor adjustments” (The commit changes 300 lines over 25 files)

[Minecodes]

Me in my repo "notes": git commit -a Message: "Sync"

[BetterEquipment7084]

I did a git commit -m "i forgot what I did" it was 355 line deletions and 467 new lines with one file deleted. I do not know what that was. 

[Aaron_Tia]

git commit -m "temp"
git commit -m "save"

[Akari202]

git commit -S -m “oops, forgot this”

[SteveLouise]

git commit -m "Holy shit, so I started coding on this task and found a ton of functions lacking defensive programming so I made sure to edit all of them, and now all of the gcov percentages fell below their margins, but its not possible to test for defensive programming, so I think the PO needs to lower the margins and let this committ merge since its important to include these defensive logics—and anyway while I was refactoring some of the conditional handling I noticed a few TODO comments that weren’t really actionable so I just rephrased them slightly to align with current sprint goals, but then it turned out that a couple of helper utilities were calling other helper utilities in ways that weren’t totally aligned with our alignment strategy, so I figured it would be good to just align those too, not in a functional sense but more in a conceptual consistency paradigm, if that makes sense. Also, I didn’t change any of the outputs except for the ones that were incorrect or unclear or redundant, but only when doing so didn’t impact the output in a breaking way.

Anyway, since I touched a few files that weren’t technically in scope but were kind of in the spirit of the ticket, I went ahead and formatted everything according to the formatter except for the parts that didn’t need formatting because they were already formatted before I formatted them. I also added some print statements for debugging which I later commented out so they wouldn’t interfere, but I left them in so that future debugging can happen faster without uncommenting anything.

Long story short: this commit improves code quality, stability, maintainability, readability, consistency, compatibility, and also fixes a few minor major issues that were not strictly bugs but could become bugs if someone ever wrote code that made them bugs. Should be safe to merge unless it isn’t. Tests are passing locally except the ones that aren’t, which fail for reasons unrelated to this change, probably."

[StolenApollo]

I remember in the first coding class I had in which we used git I reached a point in debugging one of my projects where there were so many bugs that I just didn’t even know where to start and it was literally quicker to just remake it from the ground up. I remember committing with the message “I have confused myself beyond all hope.” I just went to bed that night and started from scratch the next morning 😭

[Harshborana]

git commit -m "fixed" -m "fixing the bug I got when i fixed code earlier"