Maybe a better way to track the release history of a Git repo

lijok

Or commit a file to main that represents a release and build your automations off that

unsloppable

Cool and clever. One question: what do you use your old refs for? We just delete them when we get too many.

1718627440

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.

teamolHuang

Complicated and unintuitive. Our company has a few dozens of different project repos. I just created a repo for storing deploy manifests (versions, etc. for every repos of a product), and then let our automation pipeline commit the manifest. Simple to follow and no source-unrelated crap in source repos.