From e0053741d11ba68e742be61cd985bb5a52830e70 Mon Sep 17 00:00:00 2001
From: Market Data <112879596+MarketDataApp@users.noreply.github.com>
Date: Mon, 14 Sep 2026 16:39:51 -0400
Subject: [PATCH] docs: retarget a stacked PR to main as soon as it is approved

---
 .github/ISSUE_WORKFLOW.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/.github/ISSUE_WORKFLOW.md b/.github/ISSUE_WORKFLOW.md
index 710d9ae..7398dad 100644
--- a/.github/ISSUE_WORKFLOW.md
+++ b/.github/ISSUE_WORKFLOW.md
@@ -286,6 +286,12 @@ Follow the standard bug-fixing process.
 5. [ ] **Commit**: Use message format `fix: Description (closes #NNN)`
 6. [ ] **Push**: Push the fix to the appropriate branch
 
+> **Stacking a PR on another PR?** Retarget it to `main` as soon as a reviewer
+> approves it. Do not wait for its base to merge. A PR merged into a base branch that
+> has already merged puts its work on a branch nothing points at, and the work never
+> reaches `main`. **Automatically delete head branches** is on, so GitHub retargets a
+> stacked PR when its base merges — retargeting early keeps the work off that race.
+
 ### Commit Message Format
 
 ```