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
We use this repo quite a bit on the octokit side of the house. One place where these descriptions are used are in a repo where we generate source to be used by other aspects of our JavaScript ecosystem. As you know these files, the history in this repo and the use cases around it require a significant amount of interactions - which due to file size and history can take quite a bit of time when interacting with this repo.
This repo alone can account for more than 7GB on a local disk. Due to the size and shape of this repo it might be an ideal use case for Git LFS.
One of our awesome contributors @oscard0m has made a simular proposal over on octokit/openapi. I think it's a good idea and could potentially provide value here to all of the consumers of these Open API descriptions.
If interested, the Octokit gang would love to chat about what all of this might look like implemented here. Please let @kfcampbell or me (@nickfloyd) know if you'd like to talk.
The text was updated successfully, but these errors were encountered:
Hey @github/ecosystem-api friends,
We use this repo quite a bit on the octokit side of the house. One place where these descriptions are used are in a repo where we generate source to be used by other aspects of our JavaScript ecosystem. As you know these files, the history in this repo and the use cases around it require a significant amount of interactions - which due to file size and history can take quite a bit of time when interacting with this repo.
This repo alone can account for more than 7GB on a local disk. Due to the size and shape of this repo it might be an ideal use case for Git LFS.
One of our awesome contributors @oscard0m has made a simular proposal over on octokit/openapi. I think it's a good idea and could potentially provide value here to all of the consumers of these Open API descriptions.
If interested, the Octokit gang would love to chat about what all of this might look like implemented here. Please let @kfcampbell or me (@nickfloyd) know if you'd like to talk.
The text was updated successfully, but these errors were encountered: