dittodhole/dotnet-SemVer.Stamp

Uncommitted changes - Switch to ignore

DeadlyEmbrace opened this issue · 2 comments

Would it be possible to add a switch to ignore uncommitted changes?
I have a project where temporary files are generated during the build which cause SemVer.Stamp to fail the build because there are uncommitted changes, however these changes are required for the project to build

As a workaround: Why not ignore those files from versioning?
This should make the Dirty-check succeed :)

This issue will be addressed with the upcoming release (2.0.0): Uncommitted changes are generally ignored, and do not break the stamping.
Thanks for your patience!

Best
Andreas