-
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 3 replies
-
This happens when include_all_commits is set to true, but it works fine when include_all_commits is set to false. There is something wrong with the include_all_commits parameter. |
Beta Was this translation helpful? Give feedback.
-
I didn't set |
Beta Was this translation helpful? Give feedback.
-
My url is: https://github-readme-stats.vercel.app/api/top-langs/?username=, I found your url is: https://github-readme-stats-bice-iota-93.vercel.app/api/top-langs/?username=, and I previously set include_all_commits=true but it didn't work, then set it to false or remove the include_all_commits parameter. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
@magicgopher thanks for answering me. |
Beta Was this translation helpful? Give feedback.
-
Hey @phuanggh, By the following URL https://github-readme-stats-bice-iota-93.vercel.app/api/status/pat-info you can check that your GitHub API token currently expired. Therefore, you have to generate a new one (without expiration date preferably) and replace with it value of "PAT_1" environment variable on your Vercel deployment. For the future, such error message "Downtime due to GitHub API rate limiting" always shows that something wrong with your GitHub API token. |
Beta Was this translation helpful? Give feedback.
Hey @phuanggh, By the following URL https://github-readme-stats-bice-iota-93.vercel.app/api/status/pat-info you can check that your GitHub API token currently expired. Therefore, you have to generate a new one (without expiration date preferably) and replace with it value of "PAT_1" environment variable on your Vercel deployment. For the future, such error message "Downtime due to GitHub API rate limiting" always shows that something wrong with your GitHub API token.