-
Notifications
You must be signed in to change notification settings - Fork 41.2k
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
Too big for the GitHub API #8613
Comments
So currently where is it failing? |
@M1kep I went through my server logs and found where it was failing and where I got the response from GitHub that the file was too big and to use the Git Data API. The file currently using the regular API— I'm adding another option to the list up above which is to just how the last 100 or 200 on the page rather than all. I'm guessing not many come back to see their name in the list and so long as we have the number of all who have completed it, it should still feel impactful. I'm leaning towards this option now. |
Woot, page is back up and fixed now ✨ 🍕 |
is it possible to only show the newest additions in contributors folder? |
@thegerscheffect Yep, that's what it does now, it just shows the last 100—http://jlord.us/patchwork |
As of Jan. 11th the
index.html
file became over 1MB and too large to use with the GitHub API so it is not being rebuilt with new names (though new names are still being collected). There are a few options:Use JekyllPro: Jekyll does the hefty lifting, don't get limited by APICon: users can't view the site themselves without knowing JekyllThe text was updated successfully, but these errors were encountered: