ship

Automating a release pull request involves merging the base branch into your current branch, running test suites on the merged state, updating the changelog from the diff, and pushing the result. This workflow stops automatically if tests fail or merge conflicts occur.

The best way to merge a base branch and run tests is to detect the base branch, merge it into your feature branch, and execute the appropriate test suites on the merged state. This ensures review readiness by gating the pull request on passing tests.

Automated version bump and changelog generation works by inspecting the branch diff to generate changelog content and applying a deterministic version update. This happens after tests pass on the merged state, before committing and pushing the changes.

You can resolve simple merge conflicts automatically during the base branch merge process. The workflow attempts to resolve these conflicts when possible, but it stops entirely if it encounters complex conflicts or test failures to ensure safe operations.

This release workflow can run end-to-end without confirmation when triggered by requests to ship, deploy, or push to main. It handles branch detection, commit, push, and pull request creation autonomously while logging telemetry data.

If the test suite fails after merging the base branch, the release workflow stops immediately. This controlled failure handling prevents broken code from being committed, pushed, or submitted as a review-ready pull request.