Publish changes

Use Publish when your preview is ready for everyone. Publishing merges your working branch and lets the team pipeline deploy the published app.

Publish your changes

1. Open the team app.
2. Make sure your latest preview is working.
3. Select Publish in the app bar.
4. Keep the Publish window open while Fabricator works, or select Stop waiting if you only want to stop watching.

Fabricator runs these steps:

1. Save your latest changes.
2. Bring in your teammates' changes.
3. Check that your preview deploys.
4. Get a teammate's approval, when the workspace requires reviews.
5. Publish your changes.
6. Deploy the published app.

If review is required, Fabricator shows "Waiting for a teammate to approve your changes. They see your request on Fabricator's Home. Publish again once they've approved." Teammates approve from Home with View changes and Approve.

If publishing would delete data

The pipeline stops when the Rayfin CLI reports a destructive data or storage change. The GitHub workflow emits this message:

"This change would delete data in the published app. Publish it again from Fabricator and confirm to allow it."

Fabricator then shows:

"Your changes are published, but the pipeline stopped before deploying because they would delete data in the published app. Confirm to deploy anyway."

If you understand the impact, select Deploy anyway (deletes data). Fabricator dispatches the workflow again with the force input for that app.

If publish stops

Open the team menu in the header. Under Last publish, use View on GitHub when it is available. In the Publish window, use View logs on GitHub when shown.

If your preview did not deploy, Fabricator shows "Your preview didn't deploy, so Fabricator didn't publish. Open the preview's logs, fix the problem with Copilot, then publish again."

If teammates changed the same files, Fabricator shows "Your teammates changed some of the same files as you. Bring in their changes and resolve the conflicts first." Use Let Copilot combine them when it appears.