Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Consider using Git LFS

Open
#2,757 1 comment 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
git
Domain
tooling

Research direction

Start by reviewing the repository's size, history, and interactions described in the issue, then compare the proposed approach with octokit/openapi pull request 364. Define the Git LFS migration scope, effects on consumers of the OpenAPI descriptions, and the criteria for confirming that repository usage improves.

Written by the indexing model from the issue text.

Description

enhancement

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.

Dominant language
No language data
Stars
1.6k
Forks
342
Avg merge
2h 23m
Merged PRs (30d)
57

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/rest-api-description

All issues in github/rest-api-description

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.