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

Repo size #105

Open
Robinlovelace opened this issue Aug 22, 2022 · 2 comments
Open

Repo size #105

Robinlovelace opened this issue Aug 22, 2022 · 2 comments
Labels
question Further information is requested

Comments

@Robinlovelace
Copy link

Just cloned the repo and see that it's over 1/4 GB. Please consider pruning the repo size to reduce download times and save bandwidth:

gh repo clone geopython/geopython-workshop
Cloning into 'geopython-workshop'...
remote: Enumerating objects: 1770, done.
remote: Counting objects: 100% (87/87), done.
remote: Compressing objects: 100% (33/33), done.
remote: Total 1770 (delta 62), reused 64 (delta 54), pack-reused 1683
Receiving objects: 100% (1770/1770), 39.09 MiB | 1.61 MiB/s, done.
Resolving deltas: 100% (1074/1074), done.
Updating upstream
remote: Enumerating objects: 976, done.
remote: Counting objects: 100% (5/5), done.
remote: Total 976 (delta 5), reused 5 (delta 5), pack-reused 971
Receiving objects: 100% (976/976), 255.45 MiB | 1.94 MiB/s, done.
Resolving deltas: 100% (517/517), completed with 4 local objects.
From https://github.com/GISMentors/geopython-english
 * [new branch]      master     -> upstream/master
@justb4
Copy link
Member

justb4 commented Jun 4, 2023

@Robinlovelace true, part is due that we forked from an existing workshop and almost rewrote it. And there may have been some large data files pushed then deleted by accident. So all that history is carried. In the documentation we recommend to download the master zip file, which should be smaller, around 6.6MB:

https://geopython.github.io/geopython-workshop/#installation

curl -O https://codeload.github.com/geopython/geopython-workshop/zip/master
unzip master

On my system the workshop tree with .git history is around 90MB so maybe some pruning has been done. Think you also can clone just the master branch, to save.

@justb4 justb4 added the question Further information is requested label Jun 4, 2023
@Robinlovelace
Copy link
Author

No problem and thanks for the suggestions @justb4. I still think it's worth considering reducing the repo size as it will encourage contributions from the community if the codebase is easy to clone and work with.

Great work in any case, looking forward to trying updated versions of this course.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants