git clone pulls weight files as well by default
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 604
- Forks
- 66
- PR merge metrics
- No merged PRs in 30d
Description
I wonder if it would make sense to move the model files to their own repo or if there's a way to not have them pull by default.
Basically, this is a tad annoying haha.
```
Cloning into 'openl3'...
remote: Enumerating objects: 1460, done.
remote: Counting objects: 100% (44/44), done.
remote: Compressing objects: 100% (36/36), done.
Receiving objects: 24% (357/1460), 444.15 MiB | 2.55 MiB/s
```
Contributor guide
No contributing guide indexed for this repository
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
Inspect the repository layout and identify where the model files are stored and included in the clone. Compare the separate-repository idea with a way to keep model files out of the default checkout. Done means a fresh clone no longer downloads the large weight files by default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100