Document branch deletion feature in web editor

guides/branches.mdx

@@ -8,7 +8,7 @@
 
 Branches let you create separate instances of your documentation to make changes, get reviews, and try new approaches before publishing. Your team can work on branches to update different parts of your documentation simultaneously without affecting what users see on your live site.
 
 The following diagram shows an example of a branch workflow where a feature branch is created, changes are made, and then the feature branch is merged into the main branch.
 
 ```mermaid
 gitGraph
@@ -26,7 +26,7 @@
     commit id: "Live docs"
 ```
 
 We recommend always working from branches when updating documentation to keep your live site stable and enable review workflows.
 
 ## Branch naming conventions
 
@@ -123,3 +123,31 @@
 ## Merge branches
 
 Once your changes are ready to publish, create a pull request to merge your branch into the deployment branch.
+
+## Delete a branch
+
+After merging a branch, you can delete it to keep your repository organized.
+
+<Tabs>
+  <Tab title="Using web editor">
+    After your pull request is merged, the web editor displays a notification that the branch has been merged. Click **Delete branch** to remove the branch from your repository.
+
+    <Note>
+      You cannot delete the deploy branch or the repository's default branch (usually `main`).
+    </Note>
+  </Tab>
+
+  <Tab title="Using local development">
+    Delete a branch locally and remotely:
+
+    ```bash
+    # Delete the local branch
+    git branch -d branch-name
+
+    # Delete the remote branch
+    git push origin --delete branch-name
+    ```
+
+    Use `-D` instead of `-d` to force delete a branch that hasn't been merged.
+  </Tab>
+</Tabs>