I see the benefit of that and did some research into it, but I haven't done it for any of my projects because to me, there's some value in the fact that it makes me manually set the build number because it keeps me from auto-incrementing a patch number on something that should be called a minor version upgrade or a major version upgrade. After a couple weeks, I've gotten in the habit of upgrading the build number.
Yes and no.
I see the benefit of that and did some research into it, but I haven't done it for any of my projects because to me, there's some value in the fact that it makes me manually set the build number because it keeps me from auto-incrementing a patch number on something that should be called a minor version upgrade or a major version upgrade. After a couple weeks, I've gotten in the habit of upgrading the build number.
Take a look at this GitLab CI script, though. It shows how to autoincrement and save an env variable.
That's a good point. Thanks :)