this post was submitted on 27 Jun 2024
423 points (95.5% liked)

Programmer Humor

19282 readers
653 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
423
Coomitter be like (lemm.ee)
submitted 3 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
[–] RustyNova@lemmy.world 38 points 3 months ago (8 children)

NGL I 'm a bit like that. I often do "work" commits so that my working tree is a bit more clean/I can go from working state to working state easily.

But before a PR, I always squash it, and most times it's just a single commit

[–] DacoTaco@lemmy.world 4 points 3 months ago* (last edited 3 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..

[–] verstra@programming.dev 3 points 3 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.

load more comments (1 replies)
load more comments (6 replies)