1
0
mirror of synced 2025-12-22 19:34:15 -05:00

ran the modified script/content-migrations/update-developer-site-links.js

This commit is contained in:
Sarah Schneider
2020-11-23 12:01:14 -05:00
parent de500f48e1
commit 0b6d024d25
163 changed files with 1325 additions and 1325 deletions

View File

@@ -146,4 +146,4 @@ While you can't specify custom MIME types on a per-file or per-repository basis,
### Further reading
- [{% data variables.product.prodname_pages %}](https://lab.github.com/githubtraining/github-pages) on {% data variables.product.prodname_learning %}
- "[{% data variables.product.prodname_pages %}](/v3/repos/pages)"
- "[{% data variables.product.prodname_pages %}](/rest/reference/repos#pages)"

View File

@@ -16,7 +16,7 @@ versions:
Sometimes, {% data variables.product.prodname_pages %} will not attempt to build your site after you push changes to your site's publishing source.{% if currentVersion == "free-pro-team@latest" %}
- The person who pushed the changes hasn't verified their email address. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."{% endif %}
- You're pushing with a deploy key. If you want to automate pushes to your site's repository, you can set up a machine user instead. For more information, see "[Managing deploy keys](/v3/guides/managing-deploy-keys/#machine-users)."
- You're pushing with a deploy key. If you want to automate pushes to your site's repository, you can set up a machine user instead. For more information, see "[Managing deploy keys](/developers/overview/managing-deploy-keys#machine-users)."
- You're using a CI service that isn't configured to build your publishing source. For example, Travis CI won't build the `gh-pages` branch unless you add the branch to a safelist. For more information, see "[Customizing the build](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches)" on Travis CI, or your CI service's documentation.
{% note %}