I'd rather avoid maintaining a Netlify site for each project at this time. We can get a preview by naming a branch docs*, this works well enough in practice. (Yes, it overwrites the current dev documentation, need to keep in mind to have only one docs branch at any time.)

Ok, however you could have a Netlify site for all your packages, i.e. reuse the site ID in several repos. 😇

I'd like to learn more about this. Is this approach documented somewhere?

• workflow itself https://github.com/r-lib/pkgdown/blob/215f440342e2b34ab92776f9b01d25d3cbf728aa/.github/workflows/pkgdown.yaml#L61 (seen also in https://github.com/ropensci-review-tools/pkgcheck/blob/main/.github/workflows/pkgdown.yaml which is closer to what fledge need as pkgdown's own pkgdown workflow installs pkgdown as the local package, obviously 😁 ) It builds the site on gh-pages for the default branch, and for internal PRs (PRs from forks do not have access to repo secrets) it deploys a Netlify preview.
• one needs a Netlify token (developer-based) and a Netlify side ID. Netlify pricing is per team so as long as you don't go other 300 build minutes per month things are ok which is why I think you'd be fine re-using a site ID. https://docs.netlify.com/accounts-and-billing/billing/#builds-usage The URL to the preview is posted as commit status. It's very handy.

with a free plan you can add at least one collaborator (maybe not more) per team so another person could be able to generate the token.

Also relevant, one can set the two Netlify secrets for a whole GitHub organization https://docs.github.com/en/actions/security-guides/encrypted-secrets#creating-encrypted-secrets-for-an-organization

Thanks. Are multiple GH repos pushing to the same Netlify site?

Not in the examples I mentioned. I can't foresee any issue (but who knows 😬 ) as each commit gets its own URL.

Should be good now.

This old thread has been automatically locked. If you think you have found something related to this, please open a new issue and link to this old issue if necessary.