Skip to content

docs: retarget a stacked PR to main as soon as it is approved #70

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MarketDataApp merged 1 commit into from
Sep 14, 2026
Merged

docs: retarget a stacked PR to main as soon as it is approved #70

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions .github/ISSUE_WORKFLOW.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

```
Expand Down
Loading