https://blog.jaraco.com/skeleton/#history-is-forever suggests that the attribution problem is unsolvable but that's only partially true. While it's not possible to preserve the authorship of each line on squash, it's possible to retrieve the original authors before doing this and list them via the Co-Authored-By trailers. This would attribute that large commit to a whole lot of people. It's also possible to use tags instead of branches for archiving (but that's not what I'm going to talk about here).
Several years ago we were migrating a bunch of content out of ansible-core into separate repos. We made a script to rewrite stuff and make those repos according to scenarios.
I was also concerned about attribution and researched retrieving the authors. My patch didn't go in, because it was last-minute. But the PR is still around and could be helpful to others facing a similar problem: https://github.com/ansible-community/collection_migration/pull/497. Later on, I also suggested this solution to a Sphinx extension: https://github.com/sphinx-contrib/spelling/issues/60#issuecomment-665287993.
https://blog.jaraco.com/skeleton/#history-is-forever suggests that the attribution problem is unsolvable but that's only partially true. While it's not possible to preserve the authorship of each line on squash, it's possible to retrieve the original authors before doing this and list them via the
Co-Authored-Bytrailers. This would attribute that large commit to a whole lot of people. It's also possible to use tags instead of branches for archiving (but that's not what I'm going to talk about here).Several years ago we were migrating a bunch of content out of ansible-core into separate repos. We made a script to rewrite stuff and make those repos according to scenarios. I was also concerned about attribution and researched retrieving the authors. My patch didn't go in, because it was last-minute. But the PR is still around and could be helpful to others facing a similar problem: https://github.com/ansible-community/collection_migration/pull/497. Later on, I also suggested this solution to a Sphinx extension: https://github.com/sphinx-contrib/spelling/issues/60#issuecomment-665287993.
TL;DR here's how one can extract such a list:
You can then stick everything into the commit message and have GitHub link the commit to all those people.