| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
a) fetch the end date from when the milestone was closed. b) limit commits to end at the corresponding tag. c) don't add extra to commit count when we're starting from an explicit tag.
Co-authored-by: Tim Hoffmann <2836374+timhoffm@users.noreply.github.com>
…815-on-v3.11.x Backport PR #31815 on branch v3.11.x (Update mailmap to latest commit)
| Back | FazBrowse Home | New Git URL |
PR summary
This was last updated in cee7684, which added new contributors up to 0b61e32. This PR handles everything up to 99ae86b.
While going through the GitHub stats pages, I found out some annoyances with how GitHub does things. Specifically, anything a contributor "does" online uses the information from the public profile. I put "does" in quotes, because while it does cover explicit actions like committing in the web browser, it also includes one action not initiated directly by a user, but instead by a maintainer: squash merging a PR. In addition, when the script asks GitHub for the authors of a PR, it returns all the authors of the original commits. This means for every PR that is squash merged, we have the chance to count it as (at least) two authors instead of one.
This means that our author count on the GitHub stats pages can sometimes be highly inflated. I have updated the script so that it works better post-release, and regenerated those pages for releases after 0b61e32. Note that in the extreme case, some of the v3.10.x pages were generated with --since v3.10.0 instead of the previous release, so there are quite a few extra not even due to duplicate authors.
All changes and reasons whyI am putting accounts in a code block so to not ping ~75 people on one PR:
AI Disclosure
None
PR checklist