Lesson learned today (I’m mid release) is that we ...
# development
c
Lesson learned today (I’m mid release) is that we employ quite liberally (at least at two critical points) the git
--force
flag when tagging and pushing the release tag, which has the undesired effect of gladly moving an existing release tag and start building it on a new commit. BAD idea. šŸ˜•
Due to my own errors, but it would be preferred if those errors where caught locally. šŸ˜‰
Now, thanks to the great work by @bitter-ability-32190 and @broad-processor-92400 this step will soon be automated further reducing the risk of making mistakes like this, but worth having a critical eye as soon as you see the
--force
(or
-f
as in this case) flag used with git.