-
-
Notifications
You must be signed in to change notification settings - Fork 23.3k
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
Automatic workflow for handling PAT exhaust issues #2427
Comments
@Zo-Bro-23 Those are Very good suggestions. I was going insane by having to close or answer the same issue every day. 😅 We already have a way to monitor Public Vercel downtime (see #1471 and #2178). I also proposed an action some time ago that would update #1471 if there was downtime #1989. |
@rickstaa @Zo-Bro-23 i would like to handle this issue kindle assign me as this task |
@airwakz It's Amazing that you want to contribute to our project! Unfortunately, as we improved the error message in #3273, I think this feature request is no longer needed 😅. @Zo-Bro-23 I believe we can close this? I just checked if we have other bugs or features that could qualify as Hacktoberfest entries but it looks like most have already been completed or are already assigned 🤔. We didn't have many items this year since we are focused on restructuring the code so that we can release the npm package and GitHub action. These tasks however need to be performed by the core team. |
@rickstaa can uh provide me with any task which can be under hacktoberfest |
Is your feature request related to a problem? Please describe.
There seem to be a lot of duplicate issues regarding the PAT rate limit.
Describe the solution you'd like
There are a few solutions:
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: