-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
I am unable to get anything in Notable Contribution. #505
Comments
Can you explain this Notable Contributions thing? Is it same as Organization showing in activity feed? |
It should display organizations where you committed at least once to the main branch of one of its repository. It might be slightly different than the Github feed because the lattest also displays it if you opened an issue 🙂 I haven't looked yet in depth what you reported though, it's possible that's there's an issue |
@lowlighter : I created 2 pull request in covidIndia repository last year, so it should display that org if this is not considering the latest (this yr) contribution. |
@ninjakx Yeah I think it's highly probable that only last year is taken in account. Will check if it's possible to edit the GraphQL query to load all years |
So I checked but it doesn't seem possible to get past one year without using execessively expansive API requests. I also tried to use the query NotableContributions {
user(login: "ninjakx") {
contributionsCollection {
totalRepositoriesWithContributedCommits
commitContributionsByRepository(maxRepositories: 100) {
repository {
nameWithOwner
}
}
}
}
} And I couldn't found any mention the repository you mentioned in it though, the only one reported were:
So current implementation seems to be better given that. I don't think it's really fixable (it's more an API limitation), #516 will display an empty message to say that no recent contribution in organization were found instead of displaying en empty section like you got, it'll at least be more explicit 🙂 |
Workflow:
Token Settings:
public_repo, read:org, read:user
The text was updated successfully, but these errors were encountered: