Fresh clone is 2.39Gb
Open
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 98
- Forks
- 298
- Avg merge
- 14h 38m
- Merged PRs (30d)
- 38
Description
$ git lfs migrate info --everything --pointers=ignore --top=100
migrate: Sorting commits: ..., done.
migrate: Examining commits: 100% (10215/10215), done.
*.json 3.8 GB 2221/2221 files 100%
*.xz 2.3 GB 772/772 files 100%
*.doctree 485 MB 1210/1210 files 100%
*.md 87 MB 13676/13676 files 100%
*.pdf 79 MB 11/11 files 100%
git probably can't do just a diff of the cache every day either since it's a binary file.
https://nfcore.slack.com/archives/CE7DN1U7M/p1724173642878889
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported git lfs migrate info --everything --pointers=ignore --top=100 output and review the linked nf-core Slack discussion for context. The issue does not name files, tests, a proposed approach, or a target clone size, so the completion criteria need to be clarified before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100