Skip to content

Commit 1090086

Browse files
dihydroJenoxideCopilot
dihydroJenoxide
and
Copilot
authored
Link stacked PR merge-API notes to the async merge REST endpoint (#62567)
Co-authored-by: Copilot <[email protected]> Copilot-Session: fc48eebe-a846-4e0d-a78a-359e3db86192
1 parent 52144cb commit 1090086

3 files changed

Lines changed: 3 additions & 3 deletions

File tree

‎content/pull-requests/get-started/about-stacked-prs.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -113,7 +113,7 @@ You can merge your entire stack, a single pull request, or a portion of the stac
113113
Stacks support merge commit, squash, and rebase merge methods, and they are merge-queue aware. The resulting commit history is the same as merging each pull request individually, starting from the bottom.
114114

115115
> [!NOTE]
116-
> If you merge via the API and want to use stacked pull requests, you'll need to update to use the new merge API for stacks. See [AUTOTITLE](/pull-requests/reference/stacked-pull-requests-rest-and-graphql-apis).
116+
> If you merge via the API and want to use stacked pull requests, you'll need to update to use the new merge API for stacks. See [AUTOTITLE](/rest/pulls/pulls?apiVersion=2026-03-10#merge-a-pull-request-asynchronously).
117117
118118
## Next steps
119119

‎content/pull-requests/how-tos/merge-and-close-pull-requests/merging-stacked-pull-requests.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ The merge box for a stacked pull request shows the status of the entire stack, n
2727
If the stack is not linear, for example, after changes were pushed to a lower branch or after the trunk moved ahead, a **Rebase stack** button will appear in the merge box and you'll need to rebase the stack before you can merge.
2828

2929
> [!NOTE]
30-
> * If you merge via the API and want to use stacked pull requests, you'll need to update your code to use the new merge API for stacks. See [AUTOTITLE](/pull-requests/reference/stacked-pull-requests-rest-and-graphql-apis).
30+
> * If you merge via the API and want to use stacked pull requests, you'll need to update your code to use the new merge API for stacks. See [AUTOTITLE](/rest/pulls/pulls?apiVersion=2026-03-10#merge-a-pull-request-asynchronously).
3131
> * Auto-merge is not supported for stacked pull requests.
3232
3333
## Merging using a merge queue

‎content/pull-requests/reference/stacked-pull-requests-rest-and-graphql-apis.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ The REST API exposes stacked pull requests in two ways:
2424
* **The Stacks API.** A dedicated set of endpoints to list, read, create, extend, and dissolve stacks. This is the surface for creating and modifying stacks.
2525

2626
> [!NOTE]
27-
> If you merge via the API and want to use stacked pull requests, you'll need to update your code to use the new merge API for stacks.
27+
> If you merge via the API and want to use stacked pull requests, you'll need to update your code to use the new merge API for stacks. See [AUTOTITLE](/rest/pulls/pulls?apiVersion=2026-03-10#merge-a-pull-request-asynchronously).
2828
2929
For endpoints, parameters, and schemas, see [AUTOTITLE](/rest/pulls/pulls).
3030

0 commit comments

Comments
 (0)