Managing the publication of GitHub Pages sites for your organization

You can control whether organization members can publish GitHub Pages sites from repositories in the organization and restrict the visibilities that members can choose for the sites.

Who can use this feature?

Organization owners can manage the publication of GitHub Pages sites from repositories in the organization.

GitHub Pages is available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see "GitHub’s plans."

GitHub Pages now uses GitHub Actions to execute the Jekyll build. When using a branch as the source of your build, GitHub Actions must be enabled in your repository if you want to use the built-in Jekyll workflow. Alternatively, if GitHub Actions is unavailable or disabled, adding a .nojekyll file to the root of your source branch will bypass the Jekyll build process and deploy the content directly. For more information on enabling GitHub Actions, see "Managing GitHub Actions settings for a repository."

You can choose to allow organization members to create publicly published sites, privately published sites, both, or neither. For more information about access control for GitHub Pages sites, see "Changing the visibility of your GitHub Pages site."

If you disallow publication of GitHub Pages sites, any sites that are already published will remain published. You can manually unpublish the site. For more information, see "Unpublishing a GitHub Pages site."

  1. In the upper-right corner of GitHub, select your profile photo, then click Your organizations.

  2. Next to the organization, click Settings.

  3. In the "Access" section of the sidebar, click Member privileges.

  4. Under "Pages creation", select the visibilities you want to allow and deselect the visibilities you want to disallow.

    Note

    To publish a GitHub Pages site privately, your organization must use GitHub Enterprise Cloud. For more information about how you can try GitHub Enterprise Cloud for free, see "Setting up a trial of GitHub Enterprise Cloud."

  5. Click Save.

Further reading