Message 389269 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	epicfaace
Recipients	BTaskaya, Mariatta, aeros, docs@python, epicfaace, willingc
Date	2021-03-22.01:21:42
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1616376105.28.0.42810570026.issue37860@roundup.psfhosted.org>
In-reply-to

Content
I realized there's another alternative which is probably simpler. We can use Netlify to host the deploy previews, but we can use GitHub Actions to build the documentation. This way, we won't run into the build time limits for Netlify, and we can still use Netlify to host deploy previews. We can use this GitHub Actions action: https://github.com/marketplace/actions/netlify-actions, and just add it as an additional step to our existing doc GitHub Actions workflow (https://github.com/python/cpython/blob/master/.github/workflows/doc.yml). What do you think about this approach?

I realized there's another alternative which is probably simpler. We can use Netlify to host the deploy previews, but we can use GitHub Actions to build the documentation. This way, we won't run into the build time limits for Netlify, and we can still use Netlify to host deploy previews.

We can use this GitHub Actions action: https://github.com/marketplace/actions/netlify-actions, and just add it as an additional step to our existing doc GitHub Actions workflow (https://github.com/python/cpython/blob/master/.github/workflows/doc.yml).

What do you think about this approach?

History
Date	User	Action	Args
2021-03-22 01:21:45	epicfaace	set	recipients: + epicfaace, docs@python, willingc, Mariatta, BTaskaya, aeros
2021-03-22 01:21:45	epicfaace	set	messageid: <1616376105.28.0.42810570026.issue37860@roundup.psfhosted.org>
2021-03-22 01:21:45	epicfaace	link	issue37860 messages
2021-03-22 01:21:42	epicfaace	create