My private contributions have not been counted in the card

[walifile]

I'm having trouble displaying my private commits on my GitHub README despite deploying my own instance and granting all permissions when creating a token. Has anyone encountered a similar issue or found a solution? I've double-checked my settings, but still can't seem to get it to work. Any insights or suggestions would be greatly appreciated!

[qwerty541]

Hey, @walifile! Make sure that you enabled repo and user permissions for your personal access token.

[qwerty541]

Currently README file in your GitHub profile contains two cards with links on the following deployments: https://github-readme-stats.vercel.app and https://github-readme-stats-eta-green.vercel.app. https://github-readme-stats.vercel.app is public deployment which does not have access to your private contributions and never will. The next one https://github-readme-stats-eta-green.vercel.app. as I understand. it is your deployment. You can visit the following URL https://github-readme-stats-eta-green.vercel.app/api/status/pat-info to check that it currently using expired token and doesn't work. Now you need to update PAT_1 environment variable value on your Vercel deployment with new personal access token which you have recently created and than replace https://github-readme-stats.vercel.app with https://github-readme-stats-eta-green.vercel.app in your README.

[walifile]

@qwerty541 I have updated the access token in the environment variable (PAT_1) on my Vercel deployment. However its still showing as expired. I have double-check the token and ensure its correctly configured. Please help me on this.

For the time being I have included both URLs in my README. The one pointing to https://github-readme-stats.vercel.app/ is for public deployments, while the one pointing to https://github-readme-stats-eta-green.vercel.app/ is intended for private access. I will remove the public URL once the private deployment is functioning correctly. Thanks for your patience

[qwerty541]

If you sure that both of your personal access token and envorinment variable was created and configured correctly, then you can try to redeploy your vercel instance. Redeploy happens automatically when you pushing to the deployment branch in your forked repository, so you can just merge latest changes from upstream repository into master branch of your fork. Also you can perform redeploy using Vercel CLI https://vercel.com/docs/cli/redeploy.

In case if deployment still show that your token is expired after completing these steps, then it is something wrong with your token. You can try to create a new token without expiration date.

Also please clarify whether you are using classic or fine-grained personal access token.

[walifile]

@qwerty541 Success :) I managed to resolve the issue by deleting the project from Vercel and redeploying it. If you have any questions feel free to ask. Otherwise I will be closing the discussion and I wil create a YouTube video on this as well. Thanks for the guidance.

[qwerty541]

I'm glad that you have resolved your issue. Please, mark this discussion as answered if you don't need further assistace.