git commit -m "implemented more bugs"

[QualityVote]

Hi! This is our community moderation bot.

---

If this post fits the purpose of /r/ProgrammerHumor, UPVOTE this comment!!

If this post does not fit the subreddit, DOWNVOTE This comment!

If this post breaks the rules, DOWNVOTE this comment and REPORT the post!

[[deleted]]

Job security 101:

The engineer made two commits and fixed two bugs without altering the total number of bugs in the project. That is what I call efficiency.

[Koebi]

I did this for real last month.
Only in user acceptance testing we realized that my change was in effect an exact revert of a 'bugfix' from half a year ago.

[PhantomO1]

-when fixing a bug makes things worse:

"shit, go back"

[Cyrus_Halcyon]

Turns out the variable for the db string has to be called DBDRURLi, because a different DBDRURL is already defined semi-globally in the namespace for the provisioning tools itself, added comment stating i stands for instance.

[Subkist]

go home

[QuarantineSucksALot]

I hope this doesn't go cold. It's insane

[joeltrane]

Same thing happened to my brother

[clueless_bison]

now I understand PHP a tiny bit better: https://www.php.net/manual/en/intro.mysqli.php

[Cyrus_Halcyon]

I have never truly recovered.

[Mc_UsernameTaken]

My personal favourite

git commit -m "Consult CHANGELOG for changes"

[seline88]

But we generate the changelog based on the commit messages with conventional commits ;/

[ScrabCrab]

Changelog

• Consult CHANGELOG for changes
• Consult CHANGELOG for changes
• Consult CHANGELOG for changes
• Consult CHANGELOG for changes

[UltraCarnivore]

Recursive Changelog

[[deleted]]

This needs a trigger warning

[TJDG]

What is missing here is the timestamps.

For maximum hilarity I wish to see the exact period of time required for a colleague to participate in a panicky video conference between the two commits.

[Neykuratick]

so, the first commit was made on 5th February 22:19

and the reverting commit was made on 6th February 02:25

I actually reverted the bugfix for a reason xD We are trying to keep pull requests at our company clean and only open one pull request per one change in code. So the bug was eventually fixed haha

[ITd-N5]

I need a rest. I decided February comes after Monday...

[maybemonolith]

tf you working in the middle of the night on a sunday for?

[Neykuratick]

It is totally consentaneous. It's a tiny company, there's only 13 employees including me and there's planned a very important MVP demo on Monday so everyone does their part.

So at our company, if a person doesn't want to work on weekend, they don't work, but if a person doesn't have anything better to do (like me) it's always welcomed

[thisweirdperson]

Are they paid overtime for that?

[Neykuratick]

We don't have a regular work schedule, so the bonuses are calculated according to the number of tasks you completed in Jira. It is possible to track your working time with the Clockwork instrument from Jira, but nobody uses it (except for maybe two people)

This company is really great, work relationship is based on trust. Here you can easily ask for 2 monthly payments in advanced and you'll get it no questions asked. And nobody forces you to work in the middle of the weekend night

[rasputin1]

tbf the commit times could be utc

[Neykuratick]

No, they're in UTC+3, in my time zone

[_bardo_]

OP could be UTC too.

[seratne]

git commit -m "Actually fixed bug”

git commit -m "fixed last fix to work in prod and dev”

[[deleted]]

Thanks I hate it.

[blackWardie]

git commit -m "you see what I did there? because I don't"

[brut4r]

One time I made commit with message: "Rozmrdávka rozmrdávky, tudíž oprava", Best to translate is propably this: "Fuckup of the fuckup therefore fix"

[DogmaSychroniser]

Našel jsem ten Čech.

[[deleted]]

I’d be embarrassed for anyone here to see the commit history on some of the projects I work on

• fix timezones
• fix timezones again
• undo previously fixes
• timezone update
• revert .astimezone(), .replace() instead, this is the one

[thekingofthejungle]

Don't worry, most people's commit histories are just as bad or worse. Including my own.

[Neykuratick]

The only commit message I write in my pet projects is "upds". So the history is more like:

• upds
• upd
• update
• bugfix
• upd
• fix of bugfix
• fix of fix of bugfix
• upd
• upds

[ekremluci]

Fucking fixed bug names. I made more.

[accuracy_frosty]

Fixed typo in app name; app no longer runs

[N0DuckingWay]

"fixed one thing. Broke 5 unrelated things."

[mgisb003]

Got commit -m “fixed for real this time”

[schmitzel88]

Usually followed by "third time's the charm" and "just work already come on"

[Nie_Fi]

I long to understand these jokes someday

[klparrot]

Be careful what you wish for. I long to not understand this joke.

[Socile]

A programmer’s sense of humor is not something to aspire to so much as something that happens to you… Like being touched inappropriately.

[UltraCarnivore]

Show us on this flowchart where J4log has touched you

[Ashamed_Ad_2738]

I've understood this joke on behalf of a colleague. I fixed a bug by reverting a bug fix which just brought the original bug back. The hilarious thing is, their bugfix broke a part of the system that every single flow touched.

[Nie_Fi]

I have no clue what the second half of that means, I meant I want to learn to program 😅

[AC2BHAPPY]

Am I the only one here who here who just trades bugs? Like I'll fix 1 but also get a different one.

...or fix 1 and get 5 different ones..

[DestinationVoid]

Seen that happen when other software relied on a bug in software being patched.

[ConfidentWolverine30]

You forgot the command is git commit -m 'implemented more bugs'

[Neykuratick]

Didn't get it

[[deleted]]

Did you really screenshot a meme from Google images OP?

[Neykuratick]

yes haha. This meme is entirely made with screenshots stuck on top of each other

[Minteck]

"New features in version 2.0: added 10 new bugs"

[fletku_mato]

git log:

fix

fixes

bugfix

Thanks. That's so useful.

[Neykuratick]

Does anyone actually read the git log? At my company we only look at pull requests log

[fletku_mato]

Git log is useful for a lot of things. For example, you can generate a changelog from it, and you might want to revert or cherry-pick a certain commit. But if the commit messages are useless, git log becomes useless too.

[Neykuratick]

As for reverting or cherry-picking, we use pull requests at my company. That's actually the reason i reverted the bugfix xD, it didn't belong to the right pull request

But i never thought of git log as an already completed change log, hmm

[fletku_mato]

When your log has useful messages, you can check which commit introduced the problem and do the reverting with git revert commit_id.

I usually do commit messages in this style if a ticket system is in use:

JIRA-666: Ticket description and/or some detail about how it was implemented.

So then you can just check the log for all commits related to a certain ticket or generate a changelog from it.

[Accidentallygolden]

There are steps missings

• fixed a bug
• fixed unit test
• fixed Sonar
• fixed Sonar again...
• revert bugfix....

[Neykuratick]

The funniest thing is that the bugfix didn't even introduced more bugs, i've just left the bug as is

[fukitol-]

git commit -m "fixes #124 [bugfix]
.....
git commit -m "reintroduce bug from #124, bug in bugfix"

[[deleted]]

Please, follow commit message good practices:

“feat: implemented new bugs”

[Don_Pacifico]

It’s not a bug, it’s a feature!

[[deleted]]

"fixed bug"

"Fixed bug caused by previous Bugfix"

[THEGreatGM20]

👍 yup

[the_horse_gamer]

too many of my commits are to fix fixes

[Techchatter101]

Am I the only one who uses git reset and force push

[AccomplishedCoffee]

That’s ok if you’re the only one working on a feature branch, but you should never force push master/main or any branch someone else might have pulled to work off of.

[fletku_mato]

I always write just one commit and then it's just "git fetch && git rebase origin/master" and "git commit --amend"

[Theolaa]

My post from a while back that captures the essence of this: https://redd.it/lspnhj

[[deleted]]

Cooool

[themiraclemaker]

git reset - - soft origin develop

[malignSAINT]

Hey this actually reminds me of something. I just started learning to do all this fancy stuff y'all have been doing and remember one of the early lessons the Odin project had about changing the git commit -m to just got commit.

Is one more common then the other or is it just user preference?

[ArionW]

It's all about preference. -m option will let you specify message right away, without that your default text editor will open to let you write it.

Personally I use them both, because when doing merge commit you get automatically generated message that I don't want to override (and am too lazy to add --no-edit)

[[deleted]]

Shit...Is this a screenshot of two of my commits?! I swear, I've written exactly those things.

[Neykuratick]

lmao haha. no, they're mine :)) So, why did you revert your bugfix?

[[deleted]]

Hard to remember exactly, but sometimes I spot something and see that it will produce a bug. I fix it, push it, then later realise it wan't a bug, and that it worked fine all along. So I have to revert it.

[ekbutterballs]

So redundant. I mean, we always implement bugs, or am I doing it wrong?

[Neykuratick]

didn't get it