Deployment updates

[hadley]

• pkgdown workflows need update to use pkgdown::build_site_github_pages() + GitHub pages deployment
• blogdown and bookdown text needs to be update to remove mention of netlify

[gaborcsardi]

blogdown and bookdown text needs to be update to remove mention of netlify

Is this because the examples do not support netlify any more?

[hadley]

Right. For the vast majority of use cases, github pages is the way to do, so thats what we want to steer people towards.

[gaborcsardi]

The pkgdown example workflow uses pkgdown::deploy_to_branch(), isn't that good? It calls build_site_github_pages() internally, and then github_push().

What do you mean by GitHub Pages deployment? Should we use a GH Pages deployment action instead?

[hadley]

I think we want to move away from building and deploying the site in one step, because:

• It's useful to build the site even when it's not deployed (i.e. to reveal problems in external PRs)
• It's easier to understand if all the examples use the same mechanism of deploying to GitHub pages.

[gaborcsardi]

OK, the new workflow is indeed simpler, and it is now included in v2.

[github-actions]

This issue has been automatically locked. If you believe you have found a related problem, please file a new issue and include a link to this issue