You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Move GitHub Pages build and deploy function into GitHub Actions. Probably also good to move the deploy from /docs/ to the gh-pages branch to avoid all the commits into the codebase which aren't code changes but just deployed artifacts.
The text was updated successfully, but these errors were encountered:
Ultimately you can skip committing to gh-pages completely and have the action artifacts deployed to github-pages environment without any underlying git history et al., I'll look into some starter workflows for webpack (or just npm) what's usually used today now when the #215 update brings compatibility with newer node runners.
This means that any merged PR goes straight into production. (No need for maintainers to build locally and test — which also means PR preview deployments are much needed alongside this. Too bad GH still hasn't published theirs actions/deploy-pages#180 :/…)
Move GitHub Pages build and deploy function into GitHub Actions. Probably also good to move the deploy from
/docs/
to thegh-pages
branch to avoid all the commits into the codebase which aren't code changes but just deployed artifacts.The text was updated successfully, but these errors were encountered: