Feature summary
I am after 2 Github Actions, or one clever one that can do multiple things depending on conditions.
Step 1 - Build and Package - this should run against every commit to develop or PR to develop to ensure that the code can be built and packaged.
Step 2 - if the action is triggered via a new Release/Tag it should do step 1 and then push to nuget.
Things to note:
Ideally the action would pick up the last version from the tags on the repo - tag standard should start with v and then be "semver" ish - e.g. v1.0.0
If the action is running only step 1, i.e. was triggered by a PR or a commit to develop, then it should increment the minor number for the last tag and add a -pre suffix using the build/run instance id so it's unique. This should be used during the build and packaging stage.
If the action is running because it was triggered by a tag, then the build and package part should use the new tag as the version number for build and packaging
Hopefully all makes sense
Additional details
No response
Feature summary
I am after 2 Github Actions, or one clever one that can do multiple things depending on conditions.
Step 1 - Build and Package - this should run against every commit to develop or PR to develop to ensure that the code can be built and packaged.
Step 2 - if the action is triggered via a new Release/Tag it should do step 1 and then push to nuget.
Things to note:
Ideally the action would pick up the last version from the tags on the repo - tag standard should start with v and then be "semver" ish - e.g. v1.0.0
If the action is running only step 1, i.e. was triggered by a PR or a commit to develop, then it should increment the minor number for the last tag and add a -pre suffix using the build/run instance id so it's unique. This should be used during the build and packaging stage.
If the action is running because it was triggered by a tag, then the build and package part should use the new tag as the version number for build and packaging
Hopefully all makes sense
Additional details
No response