ship

Automating git worktree to main branch deployment is handled by committing, version bumping, pushing, creating, and merging pull requests using git and gh CLI commands in a single workflow. This skill orchestrates that end-to-end lifecycle automatically.

To skip CI checks for docs-only changes in a pull request, the commit requires a `[skip ci]` flag. This skill automatically detects documentation updates and applies the necessary flag to bypass continuous integration pipelines.

Managing semantic versioning and PR merges in one step is achieved by integrating a separate versioning skill before pushing to a remote repository. The workflow bumps versions, creates the pull request, and merges it sequentially.

You need to run ruff and mypy locally to ensure code passes linting and type checks before creating a pull request. This workflow enforces CI parity by validating your Python code locally before opening a PR.

You can sync your local main branch automatically after merging a pull request. Once the remote merge completes, this workflow updates your local repository to reflect the newly deployed main branch state.

Code shipping from a worktree can fail during Git or GitHub CLI operations due to local merge conflicts or authentication errors. This workflow provides robust error handling for common gh and git command failures to safely halt the process.