-
Notifications
You must be signed in to change notification settings - Fork 783
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
Comments
Yes please! I was already wondering why the repo is so big. Alternately, the |
Yeah this had been bothering me too but I didn't have time to look into it 🙂
|
Oops, |
Moving to Netlify will require a DNS change, but we can try it out first with Netlify subdomain. |
The |
Just force-pushed to trim the branch. |
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. |
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. |
I've squashed the 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. |
It gets annoying
git pull
receives several hundred megabytes due togh-pages
branch updates.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
The text was updated successfully, but these errors were encountered: