Summary
The Pages settings screen, reachable without opening the Pages settings screen.
Everything here is a repository-settings operation — which branch and folder publish, which builder runs, which domain answers — so a site can go from off to live, or be repointed, in the same place you are already talking about the repository.
What it is
A server over the GitHub Pages API: enable or disable Pages for a repository, read its current configuration, change the source, and deploy files to the Pages branch.
What you get
- Pages enabled for a repository with the branch and path you name
- A choice between Jekyll and a GitHub Actions workflow as the build type
- The current Pages configuration and deployment status read back
- Files deployed straight to the Pages branch
- Source, build type and custom domain changed after the fact
- Pages switched off again for a repository
Requirements
A GitHub personal access token carrying the repo and public_repo scopes, plus workflow if you use the Actions build type. Node, with the project built locally before first use.