Post #428738
2026-02-26 23:25 UTC
Replies (11)
-
@mszegedy@zoner.work 2026-02-27 03:40
@nerdnz@cloudisland.nz this would have been really nice to have in like 2019. asynchronously thank you
-
@ireneista@adhd.irenes.space 2026-02-27 07:12
@nerdnz@cloudisland.nz thanks for this! it's nice to know the situation has improved since when we had to do it, and your writeup is super readable and will doubtless help people
-
@jackie@social.linux.pizza 2026-02-27 07:17
@nerdnz@cloudisland.nz the actual reason why my website jackiejude.me isn't open source is because the git history contains my deadname oops
-
@vfig@mastodon.gamedev.place 2026-02-27 09:23
@nerdnz@cloudisland.nz thats a really good writeup! simple, easy to follow, and clear about the pros and cons of each approach.
-
@eq@mas.to 2026-02-27 13:25
@nerdnz@cloudisland.nz Also useful for people that are less than happy with sharing their real name online. Thanks!
-
@ferricoxide@blahaj.zone 2026-02-27 16:08
@nerdnz@cloudisland.nz Was assuming there was going to be commit-rewriting: would that change all of your commit-history's dates? How well would this work for a repository you didn't own (or otherwise has branch- or similar "protection" enabled)? While I'm not trans, seeing solutions like this always makes curious on details, N-order effects, etc..
-
@csolisr@hub.azkware.net 2026-02-27 17:50
Makes sense that the only way to retroactively rewrite history in a repository is to, indeed, retroactively rewrite all the relevant commits and force-push them. At least you'll generally have to do it only once in your lifetime, right? ...Right?
-
@maltelau@expressional.social 2026-02-27 18:42
@nerdnz@cloudisland.nz I'm a collaborator (and cis ally) on a big open source project with a lot of non-technical committees who would not be able to handle it if we rewrote history on them. We also have a good amount of people who contributed both before and after transition. Do you think it would still be helpful to inform/suggest the mailmap thing?
-
@ryanjyoder@techhub.social 2026-02-27 19:04
@nerdnz@cloudisland.nz Oof, this sucks. Sorry to anyone who has to rewrite git history.
-
@SRAZKVT@tech.lgbt 2026-02-28 07:46
@nerdnz@cloudisland.nz this is one of the biggest issues in git imo, identity is considered immutable, which is just not realistic
-
@IceWolf@masto.brightfur.net 2026-02-28 23:51
@nerdnz@cloudisland.nz Cool!...oh you recommend filter-repo Careful with filter-repo It tries to trash your repository and then remove all the safety backups. That's why it's so adamant about "run it on a fresh clone!!!!!!!!!!!!". What if there IS no fresh clone? What if there is no remote? Then it falls over horribly, and leaves you with a broken project. filter-branch is better.