![]() This will allow you to see any build errors without deploying the changes from your pull request to your site. When you do this, we recommend that you skip any deploy steps if the workflow was triggered by the pull_request event. If you are publishing with a custom GitHub Actions workflow, in order to see build error messages in your pull request, you must configure your workflow to run on the pull_request trigger. For more information, see " About status checks." If you are publishing from a branch, when you create a pull request to update your publishing source on GitHub, you can see build error messages on the Checks tab of the pull request. For more information, see " Testing your GitHub Pages site locally with Jekyll." Viewing Jekyll build error messages in your pull request We recommend testing your site locally, which allows you to see build error messages on the command line, and addressing any build failures before pushing changes to GitHub. 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." Viewing Jekyll build error messages locally To find potential build errors, you can check the workflow run for your GitHub Pages site by reviewing your repository's workflow runs. If Jekyll does attempt to build your site and encounters an error, you will receive a build error message.įor more information about troubleshooting build errors, see " Troubleshooting Jekyll build errors for GitHub Pages sites." Viewing Jekyll build error messages with GitHub Actionsīy default, your GitHub Pages site is built and deployed with a GitHub Actions workflow run unless you've configured your GitHub Pages site to use a different CI tool. Note: It can take up to 10 minutes for changes to your site to publish after you push the changes to GitHub. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |