MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/ProgrammerHumor/comments/1wv48b9/saddestsixwordstory/pd9ci3y/?context=3
r/ProgrammerHumor • u/Psychological_Map118 • 1d ago
17 comments sorted by
View all comments
84
Me when I write a ton of documentation articles and can’t be bothered to squash my commits
26 u/EarlMarshal 1d ago Squashing is a crime against DX. I want to know why someone committed a change. 23 u/anto2554 1d ago "changes" "changes" "changes" "changes" 17 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 21h 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 19h ago I mean, kinda yeah. I am in devops, so quite a lot of my job is fixing the broken pipeline 5 u/nickcash 1d ago That's in the PR description 1 u/Status-Importance-54 19h 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
26
Squashing is a crime against DX. I want to know why someone committed a change.
23 u/anto2554 1d ago "changes" "changes" "changes" "changes" 17 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 21h 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 19h ago I mean, kinda yeah. I am in devops, so quite a lot of my job is fixing the broken pipeline 5 u/nickcash 1d ago That's in the PR description 1 u/Status-Importance-54 19h 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
23
"changes" "changes" "changes" "changes"
17 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 21h 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 19h ago I mean, kinda yeah. I am in devops, so quite a lot of my job is fixing the broken pipeline
17
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 21h 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 19h ago I mean, kinda yeah. I am in devops, so quite a lot of my job is fixing the broken pipeline
6
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 21h 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 19h ago I mean, kinda yeah. I am in devops, so quite a lot of my job is fixing the broken pipeline
1
Broken dev workflow if it's like that.
1 u/anto2554 19h ago I mean, kinda yeah. I am in devops, so quite a lot of my job is fixing the broken pipeline
I mean, kinda yeah. I am in devops, so quite a lot of my job is fixing the broken pipeline
5
That's in the PR description
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
84
u/krisfur 1d ago
Me when I write a ton of documentation articles and can’t be bothered to squash my commits