include repos by user role, rename parameters #4
Conversation
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
This commit fixes a small error in the stats-fetcher that caused the `exclude_repo` parameter values to be seen as the `ownerAffiliation` inputs.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds the "role" parameter to include repositories where the user is owner/collaborator/organization_member. This PR also renames parameters "owners" to "owner" and "repos" to "repo", to be in line with the parameter "exclude_repo".
The "role" parameter is based on work by
@developStormand@rickstaa.Note that the new "role" parameter works only with statistics items fetched via GraphQL (for now), because the REST API doesn't offer the same functionality. In the REST API, filtering by affiliation/role is only possible for the authenticated user (see also here). We could add this later, if github-readme-stats supports user authentication.