The Wayback Machine - https://web.archive.org/web/20211120125427/https://github.com/gorhill/uBlock/issues/2410
Skip to content
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

Jump to bottom

Cleanup repo #2410

Open
mathbunnyru opened this issue Feb 25, 2017 · 8 comments
Open

Cleanup repo #2410

mathbunnyru opened this issue Feb 25, 2017 · 8 comments

Comments

@mathbunnyru
Copy link

@mathbunnyru mathbunnyru commented Feb 25, 2017

Describe the issue

Downloading this repository takes a lot of time. It happens, because files like ublock_0.1.0.1.zip were added to this repo. It doesn't matter if they were deleted later - they are still in .git.

But there's a cure:
There's an utility, which works pretty well:
https://rtyley.github.io/bfg-repo-cleaner/

Please, make your repository easier to clone. Thanks.
@ghost
Copy link

@ghost ghost commented Feb 25, 2017

Why should these ublock_0.1.0.1.zip files be in the git repo anyway ? I don't know much about GitHub : isn't there a way to add them to the "Releases" page without being in the git repo ? Git is for source code, not release archives.
@mathbunnyru
Copy link
Author

@mathbunnyru mathbunnyru commented Feb 25, 2017

It seems to be possible to create releases without adding zips to repo:
https://help.github.com/articles/creating-releases/
As you can see on the 7th tip, it's easy to drag and drop some binary files to a new release.
@mathbunnyru
Copy link
Author

@mathbunnyru mathbunnyru commented Mar 15, 2017

@gorhill what do you think?
@gorhill
Copy link
Owner

@gorhill gorhill commented Mar 15, 2017

I don't really have time to investigate all this for now.
@mathbunnyru
Copy link
Author

@mathbunnyru mathbunnyru commented Mar 15, 2017

Ok, thank you for your response.
@magicgoose
Copy link

@magicgoose magicgoose commented Nov 14, 2017

It doesn't matter if they were deleted later - they are still in .git.

If you want to download only the most recent state of the repo, then you can add --depth 1 parameter to git clone command. And then it shall not download anything that's not present at the latest commit. (if I understand it correctly)
@ghost
Copy link

@ghost ghost commented Dec 8, 2017

Is this issue fixed or not an issue at all?
@Atavic
Copy link

@Atavic Atavic commented Dec 27, 2017

It's still an issue, but two workarounds are provided.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
4 participants
@gorhill @magicgoose @mathbunnyru @Atavic