Branch-based collaboration
Use branches to work on documentation updates in parallel without affecting your live site.Why use branches
- Isolate changes: Work on updates without affecting your live documentation.
- Review before publishing: Get feedback from team members before changes go live.
- Parallel work: Multiple team members can work on different branches simultaneously.
Recommended workflow
Use pull requests to propose changes and collaborate with your team before merging to your live documentation. This workflow ensures your team reviews changes before publishing and maintains a clear history of updates.1
Create a pull request
Create a pull request from the editor when you’re ready to publish your changes. See Publish changes in the web editor for more information on using pull requests.
2
Review pull requests
Review pull requests in your Git provider like GitHub or GitLab.
3
Respond to feedback
When reviewers request changes, make the requested changes and save your changes. Additional changes automatically push to the existing pull request.
4
Merge pull requests
Merge your pull request after addressing all requested changes, required reviewers approve the pull request, and any automated checks pass.
Preview deployments
Preview deployments create temporary URLs where you can see your changes before they go live.Access preview deployments
- Click Share in the editor tool bar.
- Click Preview to open the preview deployment in a new tab.
- The preview URL shows your documentation with all saved changes applied.

