meow:ship

Automate pull request creation by running a ship workflow on your feature branch that detects the base branch, runs pre-flight checks, bumps versions, generates changelog entries, and outputs a final PR URL.

Automated changelog generation works by orchestrating phase-driven pre-flight checks and version bumps on your feature branch, automatically creating changelog entries, and synchronizing documentation before finalizing the pull request.

A phase-driven ship workflow in versioning and QA is a coordinated release process that gates ship authorization through pre-flight checks and plan verification before executing version bumps, changelog updates, and PR creation with telemetry.

No, you do not need to manually detect the base branch. The automated ship workflow handles base-branch detection and merge preparation during its pre-flight checks before bumping versions and creating the pull request.

The best way to coordinate tests and documentation sync for a pull request is to use an automated ship workflow that orchestrates phase-driven pre-flight checks, runs tests, and synchronizes documentation post-PR with auditable telemetry.

Your version bump and PR creation workflow lacks auditable telemetry because it lacks a coordinated ship process that provides phase-driven pre-flight checks, documentation synchronization, and reproducible final PR tracking.