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
Distinct from "ability to preview HTML from pull requests online" (#24) we should have the ability to know ahead of time if a pull request is going to build or not. That is, do all the requirements install? Does make html work?
Currently reviewers of pull requests do these checks manually, which is tedious.
I would think we'd be able to tweak our existing GitHub Actions script added in #9 to run the build on all branches but only push to GitHub Pages if it's the "latest" branch? That is, if the pull request has been merged or if the default branch has been updated directly.
I'm open to other ideas, of course!
The text was updated successfully, but these errors were encountered:
Back when we were using "main" as a branch we made a similar commit at
407b243. Eventually as part of #44 we'll probably add this back in with
some logic about only pushing to the gh-pages branch on merge.
Distinct from "ability to preview HTML from pull requests online" (#24) we should have the ability to know ahead of time if a pull request is going to build or not. That is, do all the requirements install? Does
make html
work?Currently reviewers of pull requests do these checks manually, which is tedious.
I would think we'd be able to tweak our existing GitHub Actions script added in #9 to run the build on all branches but only push to GitHub Pages if it's the "latest" branch? That is, if the pull request has been merged or if the default branch has been updated directly.
I'm open to other ideas, of course!
The text was updated successfully, but these errors were encountered: