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

Reduce gh-pages branch size? #2472

Closed
messense opened this issue Jun 23, 2022 · 9 comments · Fixed by #2474 or #2599
Closed

Reduce gh-pages branch size? #2472

messense opened this issue Jun 23, 2022 · 9 comments · Fixed by #2474 or #2599

Comments

@messense
Copy link
Member

It gets annoying git pull receives several hundred megabytes due to gh-pages branch updates.

❯ git pull
remote: Enumerating objects: 23466, done.
remote: Counting objects: 100% (23466/23466), done.
remote: Compressing objects: 100% (2336/2336), done.
remote: Total 23466 (delta 21105), reused 23257 (delta 20905), pack-reused 0
Receiving objects: 100% (23466/23466), 214.82 MiB | 5.80 MiB/s, done.
Resolving deltas: 100% (21105/21105), completed with 2622 local objects.
From github.com:PyO3/pyo3
   53b83cccbf..ef308ffaad  main       -> upstream/main
   74f4ccd485..2d9e575e3d  gh-pages   -> upstream/gh-pages
Updating 53b83cccbf..ef308ffaad

How about only keep the latest commit in gh-pages branch?

https://github.com/peaceiris/actions-gh-pages#%EF%B8%8F-force-orphan-force_orphan

@birkenfeld
Copy link
Member

Yes please! I was already wondering why the repo is so big.

Alternately, the gh-pages can be put into a separate repo.

@davidhewitt
Copy link
Member

Yeah this had been bothering me too but I didn't have time to look into it 🙂

force_orphan seems like a good quick fix, yes please! I also wonder if we should consider moving to netlify or something similar?

@messense
Copy link
Member Author

messense commented Jun 23, 2022

https://github.com/peaceiris/actions-gh-pages#%EF%B8%8F-keeping-existing-files-keep_files

With the v3, this option does not support working with the force_orphan option. The next major release (version 4) will support this

Oops, keep_files does not work with force_orphan.

@messense
Copy link
Member Author

Moving to Netlify will require a DNS change, but we can try it out first with Netlify subdomain.

@birkenfeld
Copy link
Member

Oops, keep_files does not work with force_orphan.

The redirect step might not need force_orphan though?

@davidhewitt
Copy link
Member

davidhewitt commented Jul 23, 2022

Just force-pushed to trim the branch.

@messense
Copy link
Member Author

Looks like https://pyo3.rs/main/ somehow does not include #2499 , not sure what's going on, build the guide locally does include it.

If we going to use netlify, we can apply for a open source plan first and create a team on netlify.

@davidhewitt
Copy link
Member

Looks like we have to first create the netlify pages and then apply, to demonstrate we meet their open source plan requirements. I'm happy to give configuring netlify a shot later.

@davidhewitt
Copy link
Member

I've squashed the gh-pages branch one last time, removing all the stuff other than the versioned guide builds.

The branch pre-squash can be found in my fork at https://github.com/davidhewitt/pyo3/tree/gh-pages-20220828, should we ever need it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants