[Contributor Card Tools for Releases] ~tampering with commit history w/ Squash

During the Sept 8th TCK call, we discussed squash vs not squash and its impact on the Jakarta Releases Contributors' cards history that populates the release page cards.

Thanks to @scottmarlow, we know that TCK items might be impacted by the current clean up.
[1] https://github.com/scottmarlow/jakartaee-tck/pull/3
[2] https://github.com/scottmarlow/jakartaee-tck/tree/tckrefactor_marlow_beforesquash
[3] https://github.com/scottmarlow/jakartaee-tck/tree/tckrefactor_marlow

Andrii, the Triber behind the development of the contributor's tool, found out the follow
Conclusion: Squash is not optimal to commit history with reference to the stats used for the tool.

Quoting Andrii: "the Tool for committers is pulling all PR and commit authors with co-authors. The only issue is if commit is improperly manually squashed (without co-author contribution), or commit history was forcibly rewritten, but it's more a question of development best practices and contribution, it is hard to fix through just having raw data. (there is no even indication it even existed in that branch)"

@Dexmaster, you are most welcomed to expand your findings and Q&A as needed.

Scott, questions, shoot!

Thanks for enabling this discussion :)

Start with the referenced jakartaee-tck pull request and the before- and after-squash branches, then trace how commit and co-author data feeds the release-page contributor cards. Done requires an agreed handling for squash or rewritten history and a documented outcome for the contributor-card tool.