this post was submitted on 27 Jun 2024
422 points (95.3% liked)

Programmer Humor

19593 readers
783 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
Feyter@programming.dev
anzo@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
422
Coomitter be like (lemm.ee)
submitted 4 months ago by sag@lemm.ee to c/programmer_humor@programming.dev
44 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] DacoTaco@lemmy.world 4 points 4 months ago* (last edited 4 months ago) (2 children)

Same haha. But i use a combination of commits ( but not pushed ), ammending, fixups and usually clean it up before making a PR or pushing ( and rebase/merge main branch while at it). Its how git should be used..

[–] RustyNova@lemmy.world 5 points 4 months ago

I do push often as I'm often switching between two devices. And I do make draft PR so I got an easy git diff that I can live reference with

[–] verstra@programming.dev 3 points 4 months ago

You are not alone. This is the work git was built for.

There is a bit of benefit if you have code reviewed so separate commits are easier to review instaed of one -900 +1278 commit.