Push to GitHub.

Before you begin

• Use a saved project you can open in the editor and a plan with Pro publishing access.
• Connect the GitHub account that should receive the project. You can connect from Integrations or from the publishing dialog when prompted.
• Choose the project output you want: HTML, React or Vue. Publishing generates a complete application from the visual pages.

Choose the destination

1. 1

   Open Push

   Open the saved project and choose Push in the editor toolbar. If prompted, choose Connect GitHub and complete authorization with the intended account.

2. 2

   Create or select a repository

   Under Destination, choose Create new repository or an existing writable repository. For a new repository, enter a Repository name and choose Private or Public visibility.

3. 3

   Write the commit message

   Enter a short description of what you are publishing. Confirm the connected account and selected repository before reviewing files.

Which existing repositories can receive a push?

Choose a repository already published by this same builder project, or a repository containing only a README. Initialize an empty existing repository with a README on GitHub before trying again.

A populated application repository without this project’s publishing record is not a destination for generated push. Use Import + Sync to edit an existing codebase instead. The publishing flow also rejects repositories associated with a different builder project.

Review files, then push

1. 1

   Choose Review files

   Review the repository, default branch, and lists of files to write or remove. The review is a preparation step; it has not pushed a commit yet.

2. 2

   Check the proposed changes

   Confirm that the listed changes belong to the generated application you intend to publish. If you change the destination or project files, review the current files again.

3. 3

   Choose Push reviewed files

   Push the reviewed files. Wait for the result, then open the repository to inspect the commit and project structure.

Push later changes

Later editor changes do not push automatically. The review and push action must be repeated. If the repository changes after review, review the latest state again rather than reusing an outdated review.

1. 1

   Edit the same builder project

   Make your next changes in the editor and confirm the project is saved.

2. 2

   Select the same repository

   Open Push again and select the existing repository you previously published to. Do not choose Create new repository for an update.

3. 3

   Review and push again

   Enter an appropriate commit message, choose Review files, and inspect writes and removals before choosing Push reviewed files. If there are no file changes, the result can report that the repository is already up to date.

If a push cannot continue