Add an option to include private contributions too.

[YuheshPandian]

Hey devs, I am using GitHub Trophies for a very long period now. Can you please add a feature to include private contributions to GitHub Trophies. Like for the Trophies like stars, repos, commits, issues, pull request.

If this feature already exists please guide since I couldn't find it.

With regards,
Yuhesh Pandian

[pietrodicaprio]

As that data is, indeed, private, this project should allow users to perform a GitHub Login to grant access to that data.

Moreover, at that point the data for the specific user could be retrieved using user's token allowing for more requests without hitting the limits mentioned in #320#issuecomment-2750177010 .

This is a big change tho, with no contributions is unlikely to be implemented

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[YuheshPandian]

As that data is, indeed, private, this project should allow users to perform a GitHub Login to grant access to that data.

Moreover, at that point the data for the specific user could be retrieved using user's token allowing for more requests without hitting the limits mentioned in #320#issuecomment-2750177010 .

This is a big change tho, with no contributions is unlikely to be implemented

Ohhh I got it @pietrodicaprio I will wait for the feature then, It is not that necessary so it's fine.

Thank you,
Yuhesh Pandian

[atomiclifestyle]

Hi @YuheshPandian One way to include private contributions is to fork the repo, add your GitHub Personal Access Token in a .env file, deploy it to Vercel, and then use your deployed subdomain in your README. This also helps avoid rate limits.

This method worked for me.

[marcschaeferger]

Hi @YuheshPandian One way to include private contributions is to fork the repo, add your GitHub Personal Access Token in a .env file, deploy it to Vercel, and then use your deployed subdomain in your README. This also helps avoid rate limits.

This method worked for me.

Hi @atomiclifestyle , thanks for sharing! I thought about the same because of github-readme-stats. Did you change any particular default settings on Vercel? I'm running into an issue where downloads fail on Vercel, but they're working perfectly fine locally. Any tips would be greatly appreciated!

URL: https://github-profile-trophy-theta-ten.vercel.app/

Here are the logs:

Logs:
[21:26:09.119] Running build in Washington, D.C., USA (East) – iad1
[21:26:09.121] Build machine configuration: 2 cores, 8 GB
[21:26:09.176] Cloning github.com/marcschaeferger/github-profile-trophy (Branch: master, Commit: 08e0dcc)
[21:26:09.208] Skipping build cache, deployment was triggered without cache.
[21:26:09.724] Cloning completed: 547.000ms
[21:26:09.761] Found .vercelignore
[21:26:09.765] Removed 7 ignored files defined in .vercelignore
[21:26:09.765] /.github/FUNDING.yml
[21:26:09.765] /.github/logo.png
[21:26:09.766] /.github/workflows/close-old-issues.yml
[21:26:09.766] /.github/workflows/testing.yml
[21:26:09.766] /.gitignore
[21:26:09.766] /LICENSE
[21:26:09.766] /README.md
[21:26:11.817] Running "vercel build"
[21:26:12.289] Vercel CLI 44.6.4
[21:26:12.486] > Installing Builder: vercel-deno@3.1.0
[21:26:15.720] Downloading Deno v1.42.1 (x86_64-unknown-linux-gnu)…
[21:26:17.167] Caching imports…
[21:26:17.168] deno run --allow-all api/index.ts
[21:26:17.207] �[0m�[32mDownload�[0m https://deno.land/std@0.177.0/encoding/base64.ts
[21:26:17.248] �[0m�[32mDownload�[0m https://deno.land/std@0.130.0/streams/conversion.ts
[21:26:17.262] �[0m�[32mDownload�[0m https://deno.land/std@0.130.0/io/buffer.ts
[21:26:17.278] �[0m�[32mDownload�[0m https://deno.land/std@0.130.0/_util/assert.ts
[21:26:17.278] �[0m�[32mDownload�[0m https://deno.land/std@0.130.0/bytes/bytes_list.ts
[21:26:17.278] �[0m�[32mDownload�[0m https://deno.land/std@0.130.0/bytes/mod.ts
[21:26:17.336] �[0m�[32mDownload�[0m https://deno.land/std@0.130.0/bytes/equals.ts
[21:26:17.363] �[0m�[32mDownload�[0m https://deno.land/x/dotenv@v0.5.0/load.ts
[21:26:17.422] �[0m�[32mDownload�[0m https://deno.land/x/dotenv@v0.5.0/mod.ts
........
[21:26:18.088] Build Completed in /vercel/output [2s]
[21:26:18.148] Deploying outputs...
[21:26:31.471] Deployment completed

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 14 days since being marked as stale.