git-release-workflow

Automate git releases by staging changed files, creating a formatted commit using a template, and generating an annotated tag. This workflow handles pre-release hooks, commit message formatting, and tag patterns before previewing the final push command for execution.

Yes, the automated git workflow supports optional pre-release and post-release hooks. These scripts execute validation, tests, or deployment tasks before staging files or after generating the annotated tag and push plan.

Standardize monorepo releases by applying configuration-driven workflows with consistent tag patterns and commit message templates. The process stages changes, applies annotated tags, and previews the push command across software projects.

No, the automated git release process does not push directly. It stages files, creates the commit, generates an annotated tag, and previews the push plan displaying the remote and branch for manual execution.

Configure tag patterns and commit message templates through a configuration-driven setup. Specify tag_pattern, tag_message, and commit_message_template to automate staging, formatted commits with Co-Authored-By attribution, and annotated tagging.

You need a git repository with changed files to stage and a configuration defining your commit_message_template, tag_pattern, and optional pre_release_hook. The workflow then automates the commit, annotated tag creation, and push plan preview.