Skip to content

Placeholder PR for testing#2

Closed
abatra2-sc wants to merge 12 commits into
mainfrom
test_branch
Closed

Placeholder PR for testing#2
abatra2-sc wants to merge 12 commits into
mainfrom
test_branch

Conversation

@abatra2-sc
Copy link
Copy Markdown
Contributor

No description provided.

@abatra2-sc
Copy link
Copy Markdown
Contributor Author

/integration_tests

@abatra2-sc
Copy link
Copy Markdown
Contributor Author

/integration_tests

@abatra2-sc
Copy link
Copy Markdown
Contributor Author

/integration_tests

@abatra2-sc
Copy link
Copy Markdown
Contributor Author

/integration_tests

@abatra2-sc
Copy link
Copy Markdown
Contributor Author

/build_base_docker_images

@abatra2-sc abatra2-sc closed this Jul 5, 2024
@svij-sc svij-sc deleted the test_branch branch July 25, 2025 20:07
kmontemayor2-sc pushed a commit that referenced this pull request May 21, 2026
…, skip-blocks-descendants

Three execution-correctness fixes from the Codex review (issues #2, #3, #4 — all High):

1. Clean-worktree preflight in Step 7.

   Before any `git checkout` in --execute mode, require `git status --short` to be
   empty. Tracked local edits can otherwise follow a checkout into the new
   decomposition branch and get staged or committed by mistake. Skill now stops
   and asks the user to stash / commit / discard before continuing.

2. Cherry-pick semantics: each PR's OWN commits, exactly once.

   The previous phrasing ("cherry-pick predecessor commits") was ambiguous and
   could be read as "cherry-pick the range `main..decomp/C`". That range
   includes C's own ancestors (e.g. shared root B), so picking it after already
   picking B directly causes B's commits to replay and conflict. The skill now
   says explicitly: cherry-pick each ancestor PR's OWN commits — never full
   branch ranges — in topological order. Shared ancestors (top of a diamond)
   get cherry-picked exactly once total per dependent branch.

   Updated:
   - Step 3 basic-build example to use `<PR_A's OWN commits>` and add a
     paragraph spelling out the rule.
   - Step 3 diamond paragraph: "each ancestor PR's own commits exactly once,
     in topological order."
   - Worked example F construction: per-line comments noting that C and D each
     contain B's commits but we don't re-include them.
   - Step 7 bash block to mirror the same convention.

3. Skipping a PR may block its descendants.

   Per user clarification: skipping a parent PR defers the entire subtree
   rooted at that PR. Descendants can't be merged either — their cherry-picked
   copy of the predecessor's code is unreviewed at HEAD until the predecessor
   lands. Only independent siblings remain unblocked. Skill now explicitly
   tells the user "Skipping #N defers #M and #K (its dependents) too."

Also added three Common Mistakes entries covering each of the above so the
rules survive deadline-pressure rationalization.

mdformat clean.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant