This repository has been archived by the owner on May 5, 2024. It is now read-only.
How to handle latest
on master pushes?
#433
Unanswered
oliversalzburg
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I really love the automatic versions action, but I'm a bit confused if I'm using it properly for the "release on master pushes" scenario.
I am using the first usage example and, whenever I push a commit to master, I get a new release that will include a single change. The
latest
tag is then always moved to this last push and the next push will always also only include a single change.This behavior is counter-intuitive to me, as I would assume the
latest
tag would point to something like the last tagged release, so that the development build release will show all changes since that last tagged release.I'm wondering if I got the wrong idea how this should be used or maybe I'm just not using it correctly.
Beta Was this translation helpful? Give feedback.
All reactions