Publish changes in the web editor

Save your work and publish changes to your documentation site.

Publishing workflows

The editor supports two workflows for publishing documentation updates. The workflow you use depends on your repository’s branch protection rules and the branch you work on.

• Create pull requests: If your repository has a branch protection rule that requires pull requests before changes can merge into your deployment branch, the editor creates a pull request when you publish changes.
• Publish directly: If your repository has no branch protection rules, your changes merge to the deployment branch and deploy immediately when you publish.

Branch type	Branch protection	Publishing workflow
Deployment branch	None	Commits and deploys changes
Deployment branch	Pull requests required	Creates a pull request
Feature branch	None	Merges changes to deployment branch and deploys changes
Feature branch	Pull requests required	Creates a pull request

Configure branch protection rules in your Git provider to require pull requests. See About protected branches in the GitHub docs or Protected branches in the GitLab docs.

Save changes

As you edit, the editor tracks your changes.

• New or deleted files.
• Content edits in pages.
• Navigation structure changes.
• Media uploads and organization.
• Configuration updates.

When you work on your deployment branch, your changes save automatically.

When you work on a feature branch, you can save changes to the branch as commits.

To discard changes, click Undo changes beside a file name in the Changes dropdown.

Publish your changes

Click Publish in the toolbar. Depending on your workflow, your changes deploy immediately or create a pull request for you to merge in your Git provider. If you are on a feature branch, save your changes before publishing.

The Publish button is disabled when there are no pending changes or when a pull request for the current branch is already open.

Resolve conflicts

Conflicts occur when your branch and the deployment branch have incompatible changes to the same files.

What causes conflicts

Conflicts happen when:

• You and another team member edit the same lines in a file.
• Files are moved or deleted in one branch but modified in another.

Resolve conflicts

The editor displays warnings when conflicts prevent operations like publishing or switching branches. To resolve conflicts, follow the instructions in the editor to choose which changes to keep.

Commit signing

Sign commits with your GitHub account by authorizing it in your account settings. Without authorization, the Mintlify GitHub App signs commits made in the web editor.

Attributing commits to your account maintains an accurate history of who made changes to your documentation.