From 781c793de85a2f0881b23ef300076cb4da8cfd48 Mon Sep 17 00:00:00 2001 From: Nick McAvoy Date: Fri, 24 Jul 2026 14:15:47 +0900 Subject: [PATCH] mz-commit: allow upstream branches for PR stacks Stacked PRs target each other's branches, so the branches must live in MaterializeInc/materialize rather than a fork. Note the cleanup obligation after merge. Co-Authored-By: Claude Fable 5 --- .agents/skills/mz-commit/SKILL.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.agents/skills/mz-commit/SKILL.md b/.agents/skills/mz-commit/SKILL.md index fe916603c9637..4334592b30c07 100644 --- a/.agents/skills/mz-commit/SKILL.md +++ b/.agents/skills/mz-commit/SKILL.md @@ -81,6 +81,8 @@ GitHub is public. Linear is not. ## Git conventions * Work against the `main` branch of `MaterializeInc/materialize`. -* Push branches to your fork. +* Push branches to your fork. Exception: a PR stack needs its branches + in `MaterializeInc/materialize`, since each stacked PR targets the + branch below it. Delete the branches once the stack merges. * Pull requests target `main` on `MaterializeInc/materialize`. * Each PR should contain one semantic change.