Avoid bloating previous author's contribution stats #107
Conversation
Otherwise GitHub counts each force-push of an amended commit as a contribution by the original author, which may lead to hundreds and thousands of "fake" contributions provided that action typically runs multiple times a day.
|
@rht, @timabbott, could you please give me some feedback? |
|
LGTM. On another note, I have one case: I have sometimes added extra commits to my archive repo for maintenance purpose (e.g. updating the GA workflow yml, readme, etc). This results in more than 1 commits to the repo, and the GA amends the last commit regardless of whether it is maintenance commit, or the commit that adds the archive HTML files. And thus results in several versions of the archive files. But this problem can be avoided by always amending the only commit in the repo anyway, even if it is for maintenance. |
Or one can use |
|
Merged, thanks folks! |
Otherwise GitHub counts each force-push of an amended commit as a contribution by the original author, which may lead to hundreds and thousands of "fake" contributions provided that action typically runs multiple times a day.
This is a #101 fixup (see #101 (comment)) and an alternative to #105.
I use my fork/branch for OSMLatvija/zulip-archive and it seems to work just fine.