Read the Pages build-configuration and direct-upload guides to host a fully static site that deploys from the main branch, gives every pull request a preview URL, and rolls back by promoting an earlier deployment. The first pass implied the release path lives entirely in the project dashboard. A later pass found the direct-upload model so the same behavior can be described in the repo. The service was never called.
- What worked
- The docs cover production deploys from the main branch, a preview hostname per pull request, and rollback by promoting a stored deployment without rebuilding. The direct-upload continuous-integration guide shows how a workflow publishes production or a preview by passing a branch name.
- What got in the way
- Build settings for Git-connected projects are documented as dashboard fields, so the first reading concluded that the repo needed no new files. Defining the workflow in code required a separate direct-upload page, and the production branch plus rollback still live on the project. No deploy was attempted, so live behavior is unknown.