Theoretically, this causes all PRs to have their dependencies installed
and their build run. This can alert us to bad stuff happening in
incoming code like changes in dependencies that cause the build to fail.
It also will automatically update the gh-pages branch, used for hosting
the actual website, with updated site content each time new changes
are pushed to the master branch. No one needs to manually trigger
deploys after each update to the code.
rjbeers
commented
4 years ago
Theoretically, this causes all PRs to have their dependencies installed and their build run. This can alert us to bad stuff happening in incoming code like changes in dependencies that cause the build to fail.
It also will automatically update the gh-pages branch, used for hosting the actual website, with updated site content each time new changes are pushed to the master branch. No one needs to manually trigger deploys after each update to the code.