Merge renamed contributor accounts into one canonical username - #344
Open
abdalraof-albarbar wants to merge 3 commits into
Open
Merge renamed contributor accounts into one canonical username#344abdalraof-albarbar wants to merge 3 commits into
abdalraof-albarbar wants to merge 3 commits into
Conversation
|
@abdalraof-albarbar is attempting to deploy a commit to the tscircuit Team on Vercel. A member of the Team first needs to authorize it. |
pr-analysis/2026-07-07.json really contains PRs cached under both a contributor's old login (technologyet31-create) and their new one (abdalraof-albarbar) after a GitHub rename, so the tracker counts one person as two. loadPrAnalysis returns them under two logins; the test asserts they should load under one. It's marked test.failing so CI stays green until the fix lands. Co-authored-by: abdalrouf-AAA <236259618+technologyet31-create@users.noreply.github.com>
When someone renames their GitHub account, old PRs, weekly overviews and cached analyses keep the old login while new data uses the new one, so the tracker counts them as two contributors: split overview cards, split PRs by contributor, and split sponsorship totals. Add a small contributor-aliases map and getCanonicalUsername(), and apply it everywhere contributors are aggregated - overview generation, cached PR analyses (so regenerated markdown/README and the stored JSON heal to the canonical login), the frontend tables/graph, and the monthly sponsorship CSV - so a rename no longer splits someone in two. Future renames just need one line in contributor-aliases. Co-authored-by: abdalrouf-AAA <236259618+technologyet31-create@users.noreply.github.com>
The fix canonicalizes cached logins on load, so the repro from the previous commit now passes - drop test.failing and the temporary bun-types shim. Co-authored-by: abdalrouf-AAA <236259618+technologyet31-create@users.noreply.github.com>
abdalraof-albarbar
force-pushed
the
merge-renamed-contributor-usernames
branch
from
July 10, 2026 22:09
e2bfd69 to
a9684a2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When someone renames their GitHub account the tracker splits them in two — old PRs, weekly overviews and cached analyses keep the old login while new data uses the new one, so you end up with two overview cards, two "PRs by contributor" groups, and split sponsorship totals for one person.
This adds a small
contributor-aliasesmap +getCanonicalUsername()and applies it wherever contributors are aggregated: overview generation and cached PR analyses (so regenerated markdown/README and the storedpr-analysisJSON heal to the canonical login), the frontend tables/graph, and the monthly sponsorship CSV. Merge helpers are factored intolib/merge-contributor-stats.tswith unit tests. Future renames are just one line incontributor-aliases.