project-orchestrator:finishing-branch

Automating pull request creation and changelog updates when finishing a branch involves coordinating pre-merge test verification, preparing changelog entries, and ordering multi-service PRs. This process streamlines finalizing development work by validating tests and presenting PR options to ensure safe, repeatable merges.

Sequencing pull requests across a polyrepo project requires guiding per-service PR ordering based on service-level worktrees. The finalization process adapts to multi-service setups, handling base-branch rebases and conflict guidance to coordinate PR workflows across repositories for clean, auditable finishes.

Handling base-branch rebases and merge conflicts before opening a pull request requires guidance during the branch finalization process. The workflow coordinates base-branch rebase operations, provides conflict guidance, and enforces post-finish cleanup to ensure worktrees remain in clean states before merging.

Pre-merge test validation can be enforced across both monorepo and polyrepo layouts. The finalization workflow validates tests before merging, adapting its steps to service-level worktrees to support multi-service setups and ensure repeatable, safe merges across different repository structures.

Automated branch finishing supports auto-deploy warnings and records living-state outcomes for auditable finishes. It enforces pre-merge validations and provides auto-deploy warnings to ensure safe merges, maintaining an auditable record of the finalization process.

Automated branch finalization for pull requests should not be used when manual intervention is required for complex conflict resolution beyond basic guidance. The process enforces pre-merge validations and handles cleanups, but severe conflicts may require manual handling outside the automated workflow.