github doesn't usually show it on the website; however, the configured values for each commit do appear in the raw objects of the .git directory, of any clone:
try git cat-file commit HEAD
it's possible to "rewrite history"[1] after changing the global configs, so that these are updated in each commit, although that will change the commit IDs, which are hash roots of the commit files. if you don't require the granular history for git bisect debugging, then just rm -rf .git && git init will get rid of all the old metadata.
github doesn't usually show it on the website; however, the configured values for each commit do appear in the raw objects of the
.gitdirectory, of any clone:try
git cat-file commit HEADit's possible to "rewrite history"[1] after changing the global configs, so that these are updated in each commit, although that will change the commit IDs, which are hash roots of the commit files. if you don't require the granular history for
git bisectdebugging, then justrm -rf .git && git initwill get rid of all the old metadata.see Rewriting History and specifically _the_nuclear_option_filter_branch ↩