-
-
Notifications
You must be signed in to change notification settings - Fork 23.4k
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 think we should remove the count_private
option altogether, unless we plan to add a totalContributions
field in the future.
#2517
Comments
I agree. @anuraghazra, see my comment in #2500 (comment). |
We’re are u all from im in wa
…Sent from my iPhone
On 14 Feb 2023, at 9:27 pm, Rick Staa ***@***.***> wrote:
I agree. @anuraghazra, see my comment in #2500 (comment).
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.
|
I think that it should be left in because it is a feature with the basic default GitHub activity page. |
I think the current way of adding contributions to commits is incorrect and should be changed. Ideally, users would have the ability to show or commits or contributions. This information can be retrieved for the current year using GraphQL (see below) but, however, would be a different feature request. You are welcome to open a future request or pull request. query userInfo($login: String!) {
user(login: $login) {
name
login
contributionsCollection {
totalCommitContributions
totalIssueContributions
totalPullRequestContributions
totalPullRequestReviewContributions
restrictedContributionsCount
totalRepositoryContributions
}
}
} {"login": "rickstaa"} |
As explained in #2517 the 'include_private' flag is confusing and doesn't work as expected. This commit therefore removes this flag.
I removed this boolean in #2736 and requested a review of the other collaborators. @mrsanchez90, @RinSoftwareDeveloper or others feel free to add your review to this pull request. |
* feat: remove 'include_private' As explained in #2517 the 'include_private' flag is confusing and doesn't work as expected. This commit therefore removes this flag. * fix: fix tests * docs: remove redundant private deploy note
* feat: remove 'include_private' As explained in anuraghazra#2517 the 'include_private' flag is confusing and doesn't work as expected. This commit therefore removes this flag. * fix: fix tests * docs: remove redundant private deploy note
* feat: remove 'include_private' As explained in anuraghazra#2517 the 'include_private' flag is confusing and doesn't work as expected. This commit therefore removes this flag. * fix: fix tests * docs: remove redundant private deploy note
* feat: remove 'include_private' As explained in anuraghazra#2517 the 'include_private' flag is confusing and doesn't work as expected. This commit therefore removes this flag. * fix: fix tests * docs: remove redundant private deploy note
* feat: remove 'include_private' As explained in anuraghazra#2517 the 'include_private' flag is confusing and doesn't work as expected. This commit therefore removes this flag. * fix: fix tests * docs: remove redundant private deploy note
I think we should remove the
count_private
option altogether, unless we plan to add atotalContributions
field in the future.See #2504 (comment).
Originally posted by @Zo-Bro-23 in #2500 (comment)
The text was updated successfully, but these errors were encountered: