Document in-editor pull request approval flow

editor/branching-and-publishing.mdx

@@ -4,7 +4,7 @@
 keywords: ["editor", "branch", "publish", "pull request", "preview", "git", "merge", "deploy"]
 ---
 
 The web editor autosaves everything as you type, but your changes are only live when you choose to publish them. 
 
 What happens when you publish depends on two things: **which branch you're on** and **whether that branch requires pull requests**.
 
@@ -110,15 +110,23 @@
 
 ## Review and merge pull requests
 
-When a pull request is open for the current branch, the publish menu shows its review status:
+When a pull request is open for the current branch, the publish menu shows a review panel with:
 
-- **Approved**: A reviewer approved the pull request and it is ready to merge.
-- **Changes requested**: A reviewer has requested changes before the pull request can merge.
-- **Awaiting review**: The pull request is waiting for a reviewer.
+- The pull request title, description, and whether it is a draft.
+- The source and target branches.
+- The number of changed files.
+- The approval requirement on the deployment branch: **Approval required**, **Code owner required**, or no requirement.
+- The current review status: **Approved**, **Changes requested**, or **Awaiting review**.
 
-Click **View request** to open the pull request in your Git provider.
+Click **Open in GitHub** or **Open in GitLab** to view the pull request in your Git provider.
 
-After a reviewer approves the pull request, click **Merge and publish** to merge and deploy directly from the editor. The editor switches to your deployment branch after merging.
+After a reviewer approves a pull request, click **Merge and publish** to merge and deploy directly from the editor. The editor switches to your deployment branch after merging.
+
+### Approve pull requests from the editor
+
+For GitHub repositories, reviewers can approve open pull requests in the editor. When a pull request is open, an **Approve pull request** button appears in the review panel if your account has permission to review it. Click **Approve pull request** when the changes are ready to be merged. The review status updates to **Approved** and the **Merge and publish** action becomes available.
+
+The approve action is not available for draft pull requests, pull requests you have already approved, or GitLab merge requests. Click **Open in GitLab** to approve a merge request in GitLab.
 
 <Tip>
   Configure branch protection rules in your Git provider to require pull requests. See [About protected branches](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches) in the GitHub docs or [Protected branches](https://docs.gitlab.com/user/project/repository/branches/protected/) in the GitLab docs.
@@ -144,13 +152,13 @@
 
 ## Collaborate in real time
 
 When multiple people open the same page on the same branch, they edit together in real time. Each person's cursor and edits are visible to everyone, with avatars shown in the toolbar.
 
 - Changes from all collaborators merge automatically. Two people editing the same section won't create conflicts.
 - Undo only affects your own edits.
 - If you lose your connection, edits save locally and sync when you reconnect.
 
 When the [Mintlify agent](/agent) edits a page through the API or MCP, it appears in the editor like any other collaborator. You see the agent's avatar in the toolbar and a live cursor at its most recent edit location. The cursor clears automatically after the agent finishes.
 
 ## Git sync