You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have questions about stdlib? Need help fixing a bug, figuring out what to do next, or just looking for feedback? Join our weekly office hours to connect with project maintainers, stay updated on the latest project news, and chat with other community members. This is a great opportunity to ask questions, share ideas, and engage directly with the stdlib team.
Had a question regarding this PR: PR
When i was trying to push develop branch to github to sync with my fork, it failed with error Unknown Word: tkjorjk
Finally, the commit was failing with error:
Error: {"message":"API rate limit exceeded for 13.71.3.97. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)","documentation_url":"https://docs.github.com/rest/overview/resources-in-the-rest-api#rate-limiting"}
Error: {"message":"API rate limit exceeded for 13.71.3.97. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)","documentation_url":"https://docs.github.com/rest/overview/resources-in-the-rest-api#rate-limiting"}
I am not sure what I should do about this.
Should we try to disable the linting for this README, or is there any other way to solve this error?
🌟 Join Us for Weekly Office Hours! 🌟
Have questions about stdlib? Need help fixing a bug, figuring out what to do next, or just looking for feedback? Join our weekly office hours to connect with project maintainers, stay updated on the latest project news, and chat with other community members. This is a great opportunity to ask questions, share ideas, and engage directly with the stdlib team.
Everyone is welcome—drop in and say hello!
Time
UTC Tue 15-Apr-2025 16:00 (04:00 PM):
or in your local time:
Links
Joining the meeting
Agenda
The text was updated successfully, but these errors were encountered: