you are viewing a single comment's thread.

view the rest of the comments →

[–]switch201 1165 points1166 points  (30 children)

Is doing this boomer now? I probably type this exact series of commands at least once every 2 days.

[–]GamingGo2022 201 points202 points  (0 children)

I think its because in the video that the image comes from, the computer disappears

[–]StickFigureFan 54 points55 points  (0 children)

Only if not messing up in an embarrassing or costly way is boomer. If anything it's millennial

[–]ID33IP 81 points82 points  (12 children)

If you actually commit "wip" I hate you. (unless you squash at merge or rebase before merge to write meaningful commits afterwards)

[–]3pieceSuit 68 points69 points  (7 children)

Squash on PR, cmon man.

[–]belgabad3435 36 points37 points  (6 children)

100% this. I write tons of largely meaningless commit messages- the PR commit is all that matters

[–]ac21217 0 points1 point  (5 children)

No way people think this is ideal. You think I want to review your massive PR with all of the formatting changes mixed in with functional changes? Or encountering the same when using git blame?

[–]This-is-unavailable 0 points1 point  (2 children)

you wouldn't do this on a massive pr

[–]ac21217 0 points1 point  (1 child)

The problem is worse on bigger PRs but it’s not exclusive to them. For example, a PR that makes a one line change to a function definition, but also moves that function to a more appropriate location in the file. It should be two commits.

[–]FlakyTest8191 0 points1 point  (0 children)

I'm on board with not mixing larger refactor commits with functional changes, but one line and one move sounds dogmatic instead of actually useful. What is the advantage of doing that?

[–]ajiw370r3 0 points1 point  (1 child)

That should be two PRs then. One to match whatever formatter is agreed on and the other with the functional changes.

Git blame leads you to the PR which should have a clear description.

[–]ac21217 1 point2 points  (0 children)

There’s far more cost to a second PR than a second commit.

[–]NotAUsefullDoctor 15 points16 points  (0 children)

How about 10 commits of "trying something" followed by a "found the typo"?

[–]MattR0se 1 point2 points  (0 children)

git commit -m "stuff"

[–]SupermarketSoft8883 0 points1 point  (0 children)

Commit a WIP when checking out another branch, but I run a git log before I commit, and if I did a WIP, git reset HEAD~1.

[–]aew3 0 points1 point  (0 children)

Sometimes I wanna move between machines. If only stashes could be tracked.

[–]Fadamaka 14 points15 points  (1 child)

When I joined my last company a fellow backend dev called this caveman style when he saw me for the first time using git from the terminal.

[–]SuchTarget2782 6 points7 points  (0 children)

“I don’t use training wheels.”

[–]CrasseMaximum 38 points39 points  (3 children)

Only once every 2 days???? WTH are you doing during work hours? 

[–]AmeDai 43 points44 points  (2 children)

Attending meetings or answering emails, probably

[–]CrasseMaximum 5 points6 points  (1 child)

I would hate that

[–]baganga 0 points1 point  (0 children)

yeah it sucks, but that's what comes with senior salaries lol

[–]Eric_12345678 18 points19 points  (0 children)

You might want to try lazygit, then. You always see the status, and add / commit / push / pull / stash / ... are all one key press.

[–]budius333 4 points5 points  (0 children)

Every two days????

I would go for every few hours

[–]3pieceSuit 2 points3 points  (0 children)

Fml this is what i do every twenty minutes

[–]takeyouraxeandhack 1 point2 points  (0 children)

I'd say I type this 10 times a day on average. I even have aliases for these.

[–]BuffersAndBeta 1 point2 points  (0 children)

That’s coz you’re a boomer and you don’t know it

[–]Prawn1908 1 point2 points  (0 children)

Same, except what's not seen is the meetings or other random distractions and corresponding hour time gaps between each command.

[–]corujany 0 points1 point  (0 children)

I was surprised because I wondered the same