Investigate effects of commits with bad emails
There is a need to allow commits with bad emails through via project import. git-fsck checks commits for consistency, and over the years more and more checks have been added to enforce integrity on git objects. This means however, that older repositories have offending commits that a newer version of Git's git-fsck will throw errors on. This is why Git provides a way to suppress those errors.
Some customers who import older repositories are getting errors because of such commits.
We already suppress some erors in gitaly through setting git config values. The most recent ask is that we suppress errors when bad email addresses are found in commits.
In Gitaly, we've already determined that this is not a problem. Gitaly will handle commits with bad emails just fine. However, we would like to ensure that commits with bad emails do not affect the rest of the Rails codebase in adverse ways.