smaqit.release-git-pr

To automate git operations for a PR-based release, you can use a skill that stages changes, commits with a specific message, and pushes via the report_progress tool to ensure secure credential handling in CI/CD environments.

A PR title triggers post-merge automation by being correctly formatted to match specific patterns, which allows subsequent automated release steps like tagging and building to execute once the PR is merged to main.

The best way to securely push release commits in a CI/CD pipeline is by utilizing the report_progress tool, which handles git credentials securely during the staging, committing, and pushing process.

Yes, you can use this automated release process for version bumps and changelog updates. It commits these changes and pushes them to the PR branch, setting up the PR to automatically trigger builds and tagging.

No dependencies are required to automate staging and pushing code changes for a release. The skill operates independently to handle git operations and PR title formatting for post-merge automation.

You should format PR titles correctly when pushing release changes to ensure the title successfully triggers subsequent automated release steps, such as automated tagging and building, after the PR is merged.