Topic
Everything filed under git-tags, across every section.
A practical guide to choosing between Git tags and GitHub Releases, with workflows for source-only milestones, downloadable binaries, release notes, prereleases, and stable download links.
GitHub’s legacy tag protections were migrated to tag rulesets in August 2024. Use this post-migration checklist to inventory tag-targeting rulesets, verify release-tag writers and bypass actors, clean up retired API tooling, and rehearse safe tag-creation failures.
A GitHub release starts from a Git tag, but it adds a separate publication decision: notes, assets, pre-release status, notifications, and the latest-release label. Use this worked workflow to publish versioned software without deploying or announcing it at the wrong time.
GitHub tag rulesets and environment protection solve different deployment risks. This worked production flow uses both: only release managers can create immutable version tags, and only approved tags can request access to the production environment.
GitHub tag rulesets and immutable releases solve different points in a production release workflow. Use tag rulesets to control who can create, update, or delete release tags before publication, and immutable releases to preserve the published tag and assets afterward.
Immutable GitHub releases lock the release tag and uploaded assets after publication, but they do not freeze every field on the release page. Follow a before-and-after walkthrough to see exactly which corrections remain possible and how to adapt your release workflow.
GitHub tag rulesets stop unauthorized tags from being created, moved, or deleted before release publication. Immutable releases protect the tag and downloadable assets after publication; use both for v1.* production releases.
A GitHub release, its underlying Git tag, and a tag ruleset protect different parts of a software delivery process. This guide walks through a signed-version workflow, shows where immutable releases fit, and provides a decision table for selecting the right controls.
Replace retired GitHub tag protection rules with tag rulesets without accidentally blocking release automation. This checklist covers pattern inventory, fnmatch scope, safe testing, automation bypasses, and release-policy documentation.
A Git tag, a GitHub prerelease, and the Latest badge answer three different questions. Use this release engineering workflow to decide when to tag a commit, publish a prerelease, promote stable builds, and explain why tag and release dates differ.