redsub-ship

To automate a git release pipeline, this Skill enforces sequential steps: saving changes, running validation checks, bumping semantic versions across files, merging to the main branch, tagging releases, and pushing to remote repositories. It prompts for user approval at critical stages.

The best way to enforce conventional commits and semantic versioning before deployment is using an enforced release pipeline that supports commit message conventions and automatically bumps version numbers across multiple relevant project files.

To run a sequential release process for a minor version deployment, execute the skill with arguments like 'minor' and a feature description, which initiates automated validation, version bumping, and merge preparation before prompting for final push approval.

Yes, you can request code reviews and merge to the main branch automatically during CI/CD. The pipeline guides you through requesting reviews and prepares the merge, prompting for confirmation before executing the final remote repository push.

Yes, this release pipeline requires manual approval before pushing tags to a remote repository. It explicitly prompts users for confirmation at critical stages to ensure code quality and versioning accuracy prior to deployment.