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

1 comments

• lijok 1 hour ago
  Or commit a file to main that represents a release and build your automations off that
  [-]
  • gouggoug 9 minutes ago
    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)