-
Notifications
You must be signed in to change notification settings - Fork 353
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
Fixed the rate limit exceed of GitHub API on contributors page #1426
Conversation
✅ Deploy Preview for beautiify ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @ThePhoenix08, Welcome to the project Beautiify! 🎊
Thanks for your contribution! Your effort makes this project better. Keep it up! 🙌
Please wait for the PR to be reviewed. Happy Coding!! ✨
@Rakesh9100 Hey, sorry for mentioning you, but could you please review this PR. Although I had given a disclaimer above, on the dev deployment link - https://deploy-preview-1426--beautiify.netlify.app/ |
Congrats, Your pull request has been successfully merged 🥳🎉 Thank you for your contribution to my project 🚀 Keep Contributing!! ✨ @ThePhoenix08 |
Great work! The code is clear, functional, and seamlessly fixes the bug while adding the feature. Keep contributing!! @ThePhoenix08 |
Fixes Issue🛠️
Closes #1423
Description👨💻
Summary of changes made:
Type of Change📄
Checklist✅
Screenshots/GIF📷
Disclaimer
In my local development I used a dummyData.json file with the first 100 contributors data copied from one of the fetch queries done by the deployed site. But as I dont have netlify deployment, I havent tested it with nelify functions in production environment although I am confident my code will function properly in prod aswell. I will still request you to test the output of this PR in prod prior to merging in main. And let me know if just in case any issue arises.