d0edbd248f
* add first pass edits to support new pages settings /cc github/pages-engineering#383 * update with reusable * update with new step * fix break * update with www vvarient info * update with latest * apply feedback * unversion * typo * update versioning to make it render * update a few screenshots * update with remove * Apply suggestions from code review Co-authored-by: Laura Coursen <lecoursen@github.com> Co-authored-by: Meg Bird <megbird@github.com> Co-authored-by: Melanie Yarbrough <11952755+myarb@users.noreply.github.com> Co-authored-by: Laura Coursen <lecoursen@github.com>
3.5 KiB
title, intro, redirect_from, product, permissions, versions, topics
| title | intro | redirect_from | product | permissions | versions | topics | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Configuring a publishing source for your GitHub Pages site | If you use the default publishing source for your {% data variables.product.prodname_pages %} site, your site will publish automatically. You can also choose to publish your{% if currentVersion ver_lt "enterprise-server@3.0" %} project{% endif %} site from a different branch or folder. |
|
{% data reusables.gated-features.pages %} | People with admin or maintainer permissions for a repository can configure a publishing source for a {% data variables.product.prodname_pages %} site. |
|
|
For more information about publishing sources, see "About {% data variables.product.prodname_pages %}."
Choosing a publishing source
Before you configure a publishing source, make sure the branch{% if currentVersion ver_lt "enterprise-server@3.0" %} or folder{% endif %} you want to use as your publishing source already exists in your repository.{% if currentVersion ver_lt "enterprise-server@3.0" %} For example, before you can publish your project site from the /docs folder on the master branch of your repository, you or a collaborator must create a /docs folder on the default master branch of your repository.{% endif %}
{% data reusables.pages.navigate-site-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.pages.sidebar-pages %}
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
3. Under "{% data variables.product.prodname_pages %}", use the None or Branch drop-down menu and select a publishing source.
4. Optionally, use the drop-down menu to select a folder for your publishing source.
5. Click Save.
{% else %}
3. Under "{% data variables.product.prodname_pages %}", use the Source drop-down menu and select a publishing source.
{% endif %}
Troubleshooting publishing problems with your {% data variables.product.prodname_pages %} site
{% data reusables.pages.admin-must-push %}
If you choose the docs folder on {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}any{% else %}the master{% endif %} 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. For more information, see "Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites."