Most read
Ranked by anonymous view counts. No editorial weighting, no promoted placements -- just what readers are opening.
A Git tag can point to the right commit while a GitHub Release still points users at the wrong package. Learn the practical difference, then use gh CLI and Git commands to create, inspect, and verify a release with a checklist your team can repeat.
A Git tag identifies a repository snapshot; a GitHub release packages that tag for users with notes and downloadable assets. Learn why their dates differ and use a repeatable flow from verified commit to annotated tag to published release.
Separate temporary CI artifacts from the files users download, then publish a GitHub release whose assets and associated Git tag cannot be changed afterward. This checklist covers build promotion, checksums, release workflows, and the operational tradeoffs of immutability.
5 views in this window
4 views in this window
4 views in this window
4 views in this window
3 views in this window
3 views in this window
3 views in this window
3 views in this window
3 views in this window
2 views in this window
2 views in this window
2 views in this window
2 views in this window
2 views in this window
2 views in this window
2 views in this window
2 views in this window
2 views in this window
2 views in this window
2 views in this window
2 views in this window