5 ms·
There's no reason it needs to be hard in my branch before it gets merged, though. And with the way Git stores information, sometimes you don't have any option
by Uvix 2y ago
There's no reason it needs to be hard in my branch before it gets merged, though.
And with the way Git stores information, sometimes you don't have any option but to rewrite history. e.g. when something changes on a committer identity, you have to rewrite all of their commits since that information is denormalized.
- pragma_x 2y agoNow that's interesting. Are you talking about the commit author data, or something else? FWIW, this sounds like the kind of thing that signed commits would solve. If the coder/user commits anything that isn't signed, they can't push it into the origin repo in the first place.
- Uvix 2y agoYes, commit author data is what I was referring to. Both name and email address changes sometimes need to be retroactive, especially in corporate environments using GitHub or Azure DevOps.
- whoomp12342 2y agoyeah but theres no reason you have to do it that way. Just make your own local branch and squash merge it into a singular commit when ready