Publishing

Publishing turns a saved feature branch into a review request in your connected version control provider. Work can create the draft review from its result. The legacy code editor also offers a guided Publish flow.

Your workspace needs a connected repository for either flow.

Create a branch

If you're on the default branch and have changes, the system offers to create a feature branch for you. This keeps your main branch clean and lets you work on a separate branch before merging.

Commit your changes

If you have uncommitted changes, the system moves you to a commit step. The agent generates a commit message based on the diff of your changes. You can use the suggested message or write your own.

Push to remote

Work pushes each checkpoint as it runs. In the editor flow, remote changes are pulled before your local commits are pushed.

Create a pull request

Once your branch differs from its target, Infracodebase can create a draft pull request or merge request through the connected provider. The generated title and description summarize the commits, changed infrastructure resources, and expected impact.

If a review already exists for the branch, Work links it and later checkpoints continue updating the same branch. Review state from the provider appears in the Work result.

Compliance before review

Work verifies the exact saved commit before it presents the final result. A targeted or incomplete compliance result cannot satisfy the publication check. Open the linked evaluation to review findings and evidence before creating the draft review request.