Currently you can reset the build number counter easily through stage details.
Would be nice to have that as action, so you would be able to start at 0 again, if any other part of the version number is changing.
e.g in trunk, we increase the version number when having schema changes to the database, for sure this will be a "new version" but its trunk and a nightly build of trunk should reflect that by robust version pattern like:
Major.Minor.Schema.Counter
So before the change, the 67th build of the current branch might have version number:
1.2.3.67 (where 67 is the counter variable from CI)
changing something in the branch that is causing the version number to change
1.2.4.68 (build number (.NET version pattern) changed from 3 to 4), the 68 for revision part would be wrong because it should be
1.2.4.0
so having a way to set the build counter using an action, this could be fixed.
What do you think about that (well, its already there but manually).