captain-release

Automate git release workflows by running a single command that validates quality gates, commits staged changes, pushes to a captain-managed branch, and creates a versioned pull request. This ensures release integrity through enforced preconditions and automated version bumping.

A captain-driven release process coordinates branch ownership, quality validation, commit, push, pull request creation, and version management into a single automated workflow. It enforces preconditions like branch state and prior quality gates to maintain reliable deployment consistency.

Create a versioned pull request by staging changes on a captain-* branch and running the release command. The workflow automatically performs quality verification, commits the changes, pushes to the remote, bumps the version, and opens a ready-to-merge PR.

Automated release automation is scope-specific and designed exclusively for captain-managed branches. It enforces strict branch state preconditions and prior quality gate checks to maintain release consistency, meaning non-captain branches are not supported by this workflow.

The release workflow enforces quality gates before committing and pushing code. It validates branch state and prior quality checks as preconditions to ensure release integrity, preventing commits from proceeding if the quality validation fails.

Automated version bump and PR creation fails when release preconditions are not met, such as being on an invalid branch state or having prior quality gates that have not passed. The workflow enforces these strict checks to maintain release integrity before proceeding.