Repository and Pages Configuration

Publishing requires repository settings that connect source history to Pages.

The exact GitHub UI can change, so learn the concepts and verify the current labels in official GitHub Docs.

Repository decisions

Before enabling Pages, confirm:

• repository visibility is what you intend;
• no secrets/private content exist in tracked history;
• the branch you intend to publish is pushed;
• the project has a reproducible Jekyll build;
• your deployment mode is branch source or GitHub Actions.

Branch publishing concept

GitHub currently allows a branch source and supported source folder (such as repository root or /docs depending on the configured mode).

Your repository setting tells Pages which source to publish.

Actions publishing concept

For a custom Actions path, Pages source is configured for GitHub Actions and the workflow defines the build/deploy jobs.

Use the current official Jekyll workflow template as the starting point rather than copying stale YAML from this course forever.

Permissions and visibility

Pages availability/permissions can vary by repository type/account plan/organization policy.

If a classroom organization restricts Pages or Actions, that is an environment policy boundary, not a Jekyll source failure.

Public URL types

Understand the difference between a user/organization Pages root site and a project/repository Pages site because the URL/base-path model can differ.

Use the actual URL GitHub reports for your deployment.

Checkpoint

Create a deployment configuration record:

Repository:
Publishing mode:
Source branch/workflow:
Expected public URL:
Expected baseurl:
Who can change Pages settings: