Programmer Humor

19166 readers

890 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

Keep content in english
No advertisements
Posts must be related to programming or programmer topics

founded 1 year ago

MODERATORS

Feyter@programming.dev

anzo@programming.dev

BurningTurtle@programming.dev

217

Rebase Supremacy (programming.dev)

submitted 5 months ago by JPDev@programming.dev to c/programmer_humor@programming.dev

196 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] Jesus_666@feddit.de 1 points 5 months ago* (last edited 5 months ago) (1 children)

I use interactive rebases to clean up the history of messy branches so they can be reviewed commit by commit, with each commit representing one logical unit or type of change.

Mind you, getting those wrong is a quick way to making commits disappear into nothingness. Still useful if you're careful. (Or you can just create a second temporary branch you can fall back onto of you need up your first once.)

[–] bamboo@lemmy.blahaj.zone 0 points 5 months ago (1 children)

This 100%. I hate getting added to a PR for review with testing commits in the history, and I'm expected to clean those up before merging into main.

[–] Zangoose@lemmy.one 1 points 5 months ago

I feel like squash and merge on GitHub/GitLab is nicer for that anyway though, it makes the main branch so much cleaner automatically