shipRelease

Automated GitHub release workflows coordinate syncing feature branches from main, running test suites and coverage audits, pushing, and opening a PR. This removes manual choreography by validating a clean working tree and applying deterministic git flow operations before shipping.

A preflight check for shipping a git release validates a clean working tree, prevents running the process on the base branch, and loads contextual session state before touching git history. This ensures deterministic coordination between main and feature branches during the release process.

Running tests and checking code coverage before opening a pull request is handled by automated quality gates that detect the project's test runner, execute the appropriate suite, and verify coverage tooling awareness. This ensures you confidently ship releases without manual experimentation.

Automatically syncing documentation when creating a release pull request is supported by optionally triggering a documentation sync process. The release workstream pushes the branch, creates the PR, optionally updates docs, and records a release report with test, coverage, and documentation status for auditability.

Automated release coordination detects the project's existing test runner and checks for coverage tooling dynamically, so no hardcoded test framework dependencies are required. It runs the appropriate suite based on what is found in your environment before pushing the branch and opening the PR.

Running release automation directly on the main branch is blocked by preflight discipline because the workflow is designed for deterministic coordination between main and feature branches. You must invoke the release process on a feature branch to ensure changes are synced, tested, and pushed correctly.