smaqit.release-git-local

Git release automation stages specified files like CHANGELOG.md, commits them with a release message, creates an annotated Git tag for the version, and pushes both the commit and tag to the remote repository.

The best way to stage specific files for a release is to use an automated approach that safely stages only designated version files like CHANGELOG.md before committing, ensuring proper version control practices are followed without affecting other modified files.

Yes, you need Git installed and configured with appropriate repository access to push a local release commit and annotated tag. This ensures your local development release workflow has the required permissions to update the remote repository.

Yes, you can create an annotated Git tag for a specific release version after updating version files like package.json, generating a dedicated tag for the release and pushing it to the remote repository.

Using an annotated tag when pushing a local release is preferred because it stores metadata like the release message, ensuring proper version control practices are followed for your local development workflow compared to lightweight tags.

During an automated local release commit workflow, only specific release preparation files such as CHANGELOG.md and version files are safely staged, ensuring the dedicated release commit contains exactly the version control updates needed.