buck2-stack-maintainer

To automatically rebase a Buck2 fork, this tool rebases your fork/stack onto origin/main and publishes bazel-rbe-style merge commits to fork/main. It ensures upstream history is preserved as the first parent while keeping your local patch stack synchronized.

Yes, you can trigger BuildBuddy workflows for each Buck2 stack prefix. The automation triggers or polls BuildBuddy Workflows to verify changes, allowing you to quickly identify and fix failed commits during the stack maintenance process.

The best way to maintain a deterministic Buck2 patch stack is using an invariant-driven workflow. This approach rebases fork/stack onto origin/main and publishes merge commits to fork/main, ensuring the final stack merge remains testable and auditable.

Yes, you need a local Buck2 repository with valid Git remotes and access to BuildBuddy. The workflow relies on concrete invariants, specifically origin/main as upstream, fork/stack as the stack, and fork/main as the merge-commit branch.

Dry-run mode previews the maintenance plan without applying changes. You run the tool in dry-run mode to review how the Buck2 stack prefixes will be rebased and merged, then execute with apply to publish the stack prefixes.

Preserving upstream history as the first parent during a Buck2 rebase ensures the final stack merge is testable and auditable. This invariant-driven workflow publishes bazel-rbe-style merge commits to fork/main while keeping origin/main history intact.