The latest articles on DEV Community by hebrerillo (@hebrerillo). https://dev.to/hebrerillo https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1210476%2Ff154d47f-d208-43b2-aa8c-1642419705e5.png https://dev.to/hebrerillo en hebrerillo Mon, 28 Jul 2025 15:52:00 +0000 https://dev.to/hebrerillo/git-rebase-duplicated-commits-overwrite-original-commits-221m https://dev.to/hebrerillo/git-rebase-duplicated-commits-overwrite-original-commits-221m <p>Hello!</p> <p>Here is the situation. Some of my coworkers are breaking the golden rule of git: they are rebasing public branches.</p> <p>They change the hashes of public commits and do a force update.</p> <p>As a result, we have dozens of duplicate commits.</p> <p>I told them to stop doing that because duplicated commits may overwrite the original commits.</p> <p>But they asked me to prove that. Otherwise, they will keep breaking the golden rule. But I do not know how to detect such overwritten commits among the big mess that we have in the repository.</p> <p>Is there any kind of diagnosis tool for git so that it can tell you which commits are overwritten because of other duplicated commits?</p> <p>Thank you so much!</p> git