ドキュメントには頻繁に更新が加えられ、その都度公開されています。本ページの翻訳はまだ未完成な部分があることをご了承ください。最新の情報については、英語のドキュメンテーションをご参照ください。本ページの翻訳に問題がある場合はこちらまでご連絡ください。
記事のバージョン: GitHub.com

About Jekyll build errors for GitHub Pages sites

If Jekyll encounters an error building your GitHub Pages site locally or on GitHub, you'll receive an error message with more information.

GitHub Pages は、GitHub Free のパブリックリポジトリ、GitHub Pro のパブリックおよびプライベートリポジトリ、GitHub Team、GitHub Enterprise Cloud、GitHub Enterprise Server で利用いただけます。詳細は「GitHub の製品」を参照してください。

ここには以下の内容があります:

About Jekyll build errors

Sometimes, GitHub Pages will not attempt to build your site after you push changes to your site's publishing source.

Note: It can take up to 20 minutes for changes to your site to publish after you push the changes to GitHub.

If Jekyll does attempt to build your site and encounters an error, you will receive a build error message. Jekyll ビルドエラーメッセージには主に 2 つのタイプがあります。

For more information about troubleshooting build errors, see "Troubleshooting Jekyll build errors for GitHub Pages sites."

Jekyll ビルドエラーメッセージを表示する

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 "Testing your GitHub Pages site locally with Jekyll."

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. 詳しい情報についてはステータスチェックについてを参照してください。

When you push changes to your publishing source on GitHub, GitHub Pages will attempt to build your site. If the build fails, you'll receive an email at your primary email address. You'll also receive emails for build warnings.

You can see build failures (but not build warnings) for your site on GitHub in the Settings tab of your site's repository.

You can configure a third-party service, such as Travis CI, to display error messages after each commit.

  1. If you haven't already, add a file called Gemfile in the root of your publishing source, with the following content:

    source `https:/rubygems.org`
    gem `github-pages`
  2. Configure your site's repository for the testing service of your choice. For example, to use Travis CI, add a file named .travis.yml in the root of your publishing source, with the following content:

    language: ruby
    rvm:
      - 2.3
    script: "bundle exec jekyll build"
  3. You may need to activate your repository with the third-party testing service. For more information, see your testing service's documentation.

担当者にお尋ねください

探しているものが見つからなかったでしょうか?

弊社にお問い合わせください