GitHub and deployment

Understand explicit GitHub changes, previews and production delivery.

GitHub actions are deliberate

A Project may have a repository, but repository access is not implied by Workspace membership. GitHub delivery is available only in selected, configured Workspaces. When enabled, review the exact changes and explicitly request a commit or push. Pull request creation is a separate action tied to the Task’s delivered branch. A Task supports at most one pull request.

Preview before Production

Vercel delivery is limited to selected, configured Workspaces. Where enabled, a deployment request starts with a Preview. Inspect the deployed page and verify that it represents the intended revision. Production requires a separate explicit action that identifies the verified Preview source. Signing in, connecting an integration or asking generally for a deployment does not authorize Production.

Pages are a separate result path

Manifoldone Pages is available only in selected, enabled Workspaces and can publish a generated static page independently of GitHub and Vercel. Use an explicit publish action and review its confirmed status and URL. Viewing Task HTML or refreshing a local preview does not publish it.

Check the receipt

Use the recorded status, target and revision to confirm what happened. If an action has an uncertain outcome, check its existing request before trying again. Ask a Workspace administrator whether GitHub, Pages or Vercel delivery is enabled; the broader end-to-end delivery journey is not available in every Workspace.