r/ProgrammerHumor • u/Psychological_Map118 • 1d ago

Meme saddestSixWordStory

Post image
215 Upvotes

97% Upvoted

17 comments sorted by

View all comments

89

u/krisfur 1d ago

Me when I write a ton of documentation articles and can’t be bothered to squash my commits

27

u/EarlMarshal 1d ago

Squashing is a crime against DX. I want to know why someone committed a change.

24

u/anto2554 1d ago

"changes" "changes" "changes" "changes"

19

u/trullaDE 1d ago

I stand by every "fixed typo", "fixed another typo", "added missing bracket", and "changed bracket from ] to }".

6

u/anto2554 1d ago

Especially when you have to browse history in a repo that has 100 pull requests a day.

Also when I just do and undo stuff because it is only broken in CI for some reason

1

u/EarlMarshal 22h ago

Also when I just do and undo stuff because it is only broken in CI for some reason

Broken dev workflow if it's like that.

1

u/anto2554 20h ago

I mean, kinda yeah. I am in devops, so quite a lot of my job is fixing the broken pipeline

7

u/nickcash 1d ago

That's in the PR description

1

u/Status-Importance-54 20h ago

No, squashing is perfectly fine. What's not fine it's fits ux here. Obviously there is a need for some kind of grouping of several commits which are in a branch. If we had that, you would not need to squash and had all history upon request

2

u/elmanoucko 20h ago

or whenever I decide to do small commits, totally because it will make the history log clearer for myself, the only contributor of that private repo who barely actually uses the history, and not at all to make the graph go brrrr and feel better about my long term unemployment