Has anyone created a workflow with github pages to require successful deployment before merging to main brach? If so, are you willing to share? More specifically, I am imagining, a collaborator is required to create a new branch of a repo used to host a page on github pages, push changes to this other branch, and only after it is the equivalent of successfully deployed (as if it would have successfully built for a github pages), is the committer then allowed to do a pull request to the main branch for deployment of a github page. I’ve done this with a collaborative latex project (collaborators changes must be successfully run via pdflatex to compile a document before they are allowed to pull request to main), but I have not found the equivalent for hugo github page.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| A simpler way to deploy to GitHub Pages | 0 | 1301 | April 2, 2016 | |
| Simple deployment to GH Pages | 5 | 10111 | July 17, 2017 | |
| How work with github pages | 4 | 1155 | August 28, 2023 | |
| A new service to deploy to github pages. Better than Werker | 6 | 2365 | February 16, 2016 | |
| Understanding how to publish site via GitHub Pages | 1 | 1163 | May 5, 2022 |