Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
README FIRST
This commit is a draft, it requires changes to work, if this is merged without those changes, actions other than CI that attempt to build the project will fail. The fetch depth must be set to 0 for NBGV to work, as it needs the entire commit history to determine the version number. This was not done yet, as it's ultimately up to @martindevans if they would like this done or not
PR Details
This is a demo, without touching the prepare scripts, of using NBGV to manage versioning.
The build (Via Directory.Build.props), will pick up the version automagically.
The version is deterministic based on the branch and git commit height. The same commit on the same branch will generate the same version number every time.
The NuGet version for this commit would be:
0.9.3-g744be1adba
If this commit were on master, as it is currently configured, the version would be (as is:
0.9.3
, with a merge commit0.9.4
)The variables generated are trivial to use with nuget pack as well. See the build step for CI that outputs the nuget package version.
Here's a sample of the variables it generates: