Hacker News
Maybe a better way to track the release history of a Git repo
15 points by hellerve
ago
|
4 comments
1718627440
|next
[-]
You can kind of arrive at the same solution, without actually thinking about all this, by just merging into a release branch when making a release.
unsloppable
|next
|previous
[-]
Cool and clever.
One question: what do you use your old refs for?
We just delete them when we get too many.
lijok
|previous
[-]
Or commit a file to main that represents a release and build your automations off that
gouggoug
|root
|parent
[-]
One step further: use `git tag` for what it's for: tagging a given commit with an immutable reference (say, a version number like `v1.0.23`), and generate and publish "build artifacts" (`my-application-v1.0.23.tar.gz`, `my-application-v1.0.23` binary, `my-application-v1.0.23.tar.gz` helm chart, `my-application-v1.0.23` container image, `my-application-v1.0.23` ... whatever binary artifact)