-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Replaced createdAt with date of earliest repo for merged accounts #377
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…itory creation date
…ion calculations to use user activity creation date
…itory creation date
…ation in UserInfo class
…ion, and streamline earliest repository date calculation
|
@QuantumChemist is attempting to deploy a commit to the ryo-ma's Team Team on Vercel. A member of the Team first needs to authorize it. |
src/Schemas/index.ts
Outdated
| repositories(first: 100, ownerAffiliations: OWNER, orderBy: {direction: DESC, field: STARGAZERS}) { | ||
| totalCount | ||
| nodes { | ||
| name |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is no need to capture the repository name.
Please avoid capturing unnecessary information as it will increase Github's API costs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah good catch. That was a leftover from debugging. Removed it.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
LGTM |
Hi 😄 ,
at some point I had two GitHub accounts, one that I opened in 2016 and this one that I opened in 2019. Because I have merged the two accounts (i.e. transferred ownership of the repos and deleted the 2016 acc), the git-trophy would not show the correct "Experience" score for me.
That's why I replaced the createdAt object with the date of the earliest repo with createdAt as fallback.