Build with Forge

Forge deploys your committed application source with its manifest and runtime configuration. Follow Quickstart to prepare an existing repository or create a new static application.

Prepare your application

Initialize the repository with Forge to validate an existing manifest or create one for a supported static layout. Read Configure your app for the layouts initialization accepts.

Build and test your application locally, using Nexus in Codex if useful. Commit your source and manifest together, then push the intended commit to GitHub before requesting deployment.

The GitHub origin identifies the default repository, and committed HEAD identifies the default source. Automation can choose a repository, ref, or commit through the supported source selectors.

Deploy and open the result

Request deployment from your repository and complete GitHub App authorization if prompted. Keep the returned deployment reference so you can inspect its status while deployment completes.

Open the application_url returned when deployment succeeds and the route is ready. See Deploy for status guidance and CLI reference for inspection and rollback commands.

Access boundaries

Your GitHub credentials authorize source-control operations. Forge App authorization gives Forge access to the repository for deployment, without adding a deployment workflow.

Environment, tenant, account, installation, and app identity come from authorization and repository context. Review Security and trust before sharing your app.