this post was submitted on 03 Aug 2025
40 points (100.0% liked)

Programming

21924 readers
723 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
 

I want clean history, but that really means (a) clean and (b) history.

People can (and probably should) rebase their private trees (their own work). That's a cleanup. But never other peoples code. That's a "destroy history"

So the history part is fairly easy. There's only one major rule, and one minor clarification:

  • You must never EVER destroy other peoples history. You must not rebase commits other people did.

[...]

If you are working with git together with other people, it's worth a read.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] HaraldvonBlauzahn@feddit.org 4 points 5 hours ago* (last edited 5 hours ago) (3 children)

Have you ever seen or created something like this?

This might explain why it might be useful to re-write history at all, and why tools like jujutsu or gerrit are interesting, in specific contexts.

[โ€“] Flipper@feddit.org 2 points 3 hours ago

In a project I'm in there are 20 commits just labeled .. The only reason I haven't slapped them silly is they left before I started.

load more comments (2 replies)