Skip to content

feat: add P1 multi-base delivery planning - #287

Merged
Wibias merged 1 commit into
feat/p1-visual-evidencefrom
feat/p1-multi-base-delivery
Aug 18, 2026
Merged

feat: add P1 multi-base delivery planning#287
Wibias merged 1 commit into
feat/p1-visual-evidencefrom
feat/p1-multi-base-delivery

Conversation

@Wibias

@Wibias Wibias commented Aug 18, 2026

Copy link
Copy Markdown
Owner

Summary

  • add head-bound multi-base delivery planning for backports/ports
  • create one independent parallel-port identity per target base rather than treating ports as a stacked PR chain
  • bind each port to repository, source PR, exact source head SHA, and target base through deterministic provenance markers
  • keep all requested targets required by default, with explicit optional-target support
  • fail closed on invalid target refs, wrong-base provenance, and duplicate port PRs for one target
  • report multi-base delivery complete only when every required port is verified merged
  • route backport requests through a dedicated maintainer workflow while preserving separate explicit merge authority
  • expose backport/port delivery in SKILL.md discovery metadata

Hardening found during self-review

Stack

Validation

  • focused contracts cover port planning, git-style ref validation, collision-safe branch identities, provenance binding, wrong-base rejection, multi-marker ambiguity, duplicate ports, required/optional completion, routing, merge-authority separation, mutation modes, and controller phases
  • repository-wide local suite is intentionally left to the user's local run; GitHub Actions is not used as the current gate

Provenance

The multi-target delivery direction was informed by OutThisLife/brooklyn-skills delivery patterns and redesigned around GitHub Delivery's current-head, publication, merge-authority, and stacked-PR boundaries.

@coderabbitai

coderabbitai Bot commented Aug 18, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: dc875e23-3a93-4e1a-83bc-8186611cba6e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@Wibias
Wibias force-pushed the feat/p1-multi-base-delivery branch from 107bb36 to 79a492d Compare August 18, 2026 05:51
@Wibias
Wibias marked this pull request as ready for review August 18, 2026 07:46
@Wibias
Wibias force-pushed the feat/p1-multi-base-delivery branch from 79a492d to 0a7554b Compare August 18, 2026 08:00
@Wibias
Wibias force-pushed the feat/p1-multi-base-delivery branch from 0a7554b to eae874e Compare August 18, 2026 08:04
@Wibias
Wibias merged commit 165c5a7 into main Aug 18, 2026
10 checks passed
@Wibias
Wibias deleted the feat/p1-multi-base-delivery branch August 18, 2026 08:12
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