Review and publishing
Studio’s review workflow is built on GitHub pull requests. Create a PR from your content branch, review changes with your team, merge to publish, and track the deployment — all from within Studio.
Creating a pull request
Section titled “Creating a pull request”From the visual editor, click Request Review to open the pull request creation flow. Alternatively, navigate to Reviews in the Studio sidebar and create a PR manually.
Studio creates a GitHub pull request from your current branch to the main branch, automatically including a description of the changes. The PR is immediately visible in both Studio and GitHub, so collaborators can review using whichever tool they prefer.
Review queue
Section titled “Review queue”The Reviews screen lists all open pull requests for your project. Each entry in the queue shows:
| Column | Description |
|---|---|
| PR title | The title of the pull request, typically derived from the branch name or manually entered |
| Source branch | The feature branch containing the proposed changes |
| Changed files | The number of files added, modified, or deleted in the PR |
| Author | The team member who created the pull request |
Click a PR to open its detail view, or click Merge to merge it directly from the queue without navigating away.
PR detail view
Section titled “PR detail view”The detail view gives you a full pull request experience within Studio:
- Description — The PR description, editable directly from Studio
- Changed files — A list of all files included in the PR, each expandable to show a line-by-line diff
- Comments thread — A threaded discussion view for reviewing changes with your team
Add comments directly from Studio — they sync bidirectionally with GitHub, so reviewers working in GitHub see your Studio comments and vice versa. Close a PR without merging if the changes are no longer needed.
Merging and deployment
Section titled “Merging and deployment”Click Merge to merge the pull request. This triggers the GitHub Actions deployment workflow, which builds your Astro site and deploys it to Quant’s CDN.
Studio tracks the deployment in real time, showing one of four statuses:
| Status | Description |
|---|---|
| Pending | Waiting for GitHub Actions to start |
| Running | Build and deployment in progress |
| Completed | Deployment successful, with a link to the live site |
| Failed | Build or deployment error, with a link to the GitHub Actions log |
Post-merge cleanup
Section titled “Post-merge cleanup”After merging, delete the feature branch and its associated preview environment to keep your repository and Studio tidy. Studio prompts you to clean up after a successful merge, or you can manage branches manually from the branches and environments screen.
Next steps
Section titled “Next steps”- Permissions and roles — Control who can edit, review, and publish content in your Studio project
- API reference — Explore the Studio API for programmatic access to projects, content, and deployments