Export changes through a GitHub pull request
Preview the destination and generated changes before confirming a repository export.
Confirm access and the design version
Check that your organization has a working GitHub connection and access to the intended repository. Select the saved revision and completed export appropriate to the repository workflow. Your Cloud Markup role, workspace features, and GitHub installation permissions all affect availability.
Review before confirming
- Open the GitHub export workflow offered for the project or export.
- Select the intended repository and target branch.
- Generate and inspect the preview, including destination and file changes.
- Confirm only when those changes match the handoff you intend.
- Open the resulting pull request and review it through your normal GitHub process.
The repository preview is part of the approval flow. Connecting the integration alone is not authorization to publish an arbitrary set of changes.
Handle a changed destination
If the repository state changed after the preview, request a fresh preview and review it again. Do not assume a previous comparison is still valid. For a rate-limit message, honor the displayed retry timing rather than repeatedly submitting.
Keep review and deployment separate
Branch protection, required reviewers, merge decisions, and deployment remain governed by your repository and organization. Cloud Markup does not bypass those controls. For support, include the revision, export, repository and branch identifiers, error text, and whether failure occurred before or after a pull request was created.
Include this guide and what you tried in your ticket so we can pick up from there.
Contact support