Reunite performs a standard set of verification processes each time changes are made to remote content in the project.
- Changes to remote content sources that support branching, trigger verification of preview changes for branches.
- Changes to the default project branch (usually
main) or source, trigger verification of production changes.
Build logs, preview builds, and production builds are available on the Deploys page of your project's workspace.
Reunite verifies preview changes when remote files change on remote source's non-default branches.
The process has the following stages:
- A branch (for example
rem/git/rem_012345) is created in the Redocly project's repository from the project's default branch. - Changes from the remote source are applied on to that branch (for example
rem/git/rem_012345). - A preview build process runs for the
rem/git/rem_012345branch to check for errors and to generate a preview of the site with the latest changes.
Reunite automatically verifies production changes when:
- the default branch (
main) of the remote content source has changes - a remote content source that does not support branching (such as an URL source) has changes.
The process has the following stages:
- A branch (for example
rem/git/rem_012345) is created in the Redocly project's repository. - Changes from the remote source are applied on top of the new branch (
rem/git/rem_012345). - A branch build for
rem/git/rem_012345branch is created to verify that changes do not break the project. - After successful build verification, Reunite automatically merges the branch into the production branch (if Auto-merge is enabled) and starts a production build.
A pull request with changes from remote content is created automatically when:
- changes are made to the default branch of the remote content source
- changes are made to a remote content source that does not support branching (such as URL source)
Additionally, one of the following conditions must be met:
- Reunite uses a Redocly-hosted repository
- Auto-merge is disabled
Otherwise, only the branch with changes from remote content is created and merged (if Auto-merge is enabled).
Autogenerated branches are removed when:
- the remote branch is deleted
- the pull request is merged
- Remote content concepts - Understand remote content fundamentals and verification processes for ensuring content integrity and compatibility
- Set up remote content - Configure remote content for different source types with comprehensive setup guides and troubleshooting information