![]() ![]() For more information, see " Viewing workflow run history." For more information about how to re-run the workflow in case of an error, see " Re-running workflows and jobs." Publishing with a custom GitHub Actions workflow To find potential errors with either the build or deployment, you can check the workflow run for your GitHub Pages site by reviewing your repository's workflow runs. When this happens, the GitHub Actions workflow will detect the state that the branch does not need a build step, and will execute only the steps necessary to deploy the site to GitHub Pages servers. Most external CI workflows "deploy" to GitHub Pages by committing the build output to the gh-pages branch of the repository, and typically include a. Your GitHub Pages site will always be deployed with a GitHub Actions workflow run, even if you've configured your GitHub Pages site to be built using a different CI tool. For more information, see " Troubleshooting Jekyll build errors for GitHub Pages sites." If you choose the docs folder on any branch as your publishing source, then later remove the /docs folder from that branch in your repository, your site won't build and you'll get a page build error message for a missing /docs folder. Note: If you are publishing from a branch and your site has not published automatically, make sure someone with admin permissions and a verified email address has pushed to the publishing source. GitHub provides starter workflows for common publishing scenarios to help you write your workflow. If you want to use a build process other than Jekyll or you do not want a dedicated branch to hold your compiled static files, we recommend that you write a GitHub Actions workflow to publish your site. Whenever changes are pushed to the source branch, the changes in the source folder will be published to your GitHub Pages site. The source branch can be any branch in your repository, and the source folder can either be the root of the repository ( /) on the source branch or a /docs folder on the source branch. ![]() You can specify which branch and folder to use as your publishing source. If you do not need any control over the build process for your site, we recommend that you publish your site when changes are pushed to a specific branch. You can publish your site when changes are pushed to a specific branch, or you can write a GitHub Actions workflow to publish your site. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |