-
Notifications
You must be signed in to change notification settings - Fork 652
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implemented the Dirty flag #2423
Conversation
@asbjornu can you review this one as well? |
…urning the count of UncommittedChanges
@asbjornu looks like the test image for the failed one couldn't fetch the repo from github.com for some reason. Name-resolution perhaps? |
fixed |
Excellent, thank you so much for your contributions @pysco68! 🙏 |
Happy I could help :) |
🎉 This issue has been resolved in version 5.5.0 🎉 Your GitReleaseManager bot 📦🚀 |
Merge pull request #2423 from pysco68/feature/repo-dirty-flag Implemented the Dirty flag
Hello, I can't find how to use the dirty flag. assembly-informational-format: 'git-{ShortSha}-{BranchName}--{CommitDate}-{RepositoryDirtyFlag}' but no luck. Any help/doc/reference? |
@LazaroOnline, the description in the PR does not reflect what was implemented. The property changed name to |
Under the new name The only missing part I think would be at: It is nice to have this new variable, however in my case I miss some additional features related to it, |
Yes, that would be a nice addition.
It sounds like if |
Have been replacing a bunch of usages of the deprected Fody.Stamp with GitVersion lately and found that we need the "Dirty" flag as some others (see #1198). Just got ahead and implemented it.
Hope it'll meet the required project standards ;)
Description
Added a variable
RepositoryDirtyFlag
which is eithernull
orDirty
to be able to add that suffix to my version strings.Related Issue
As mentioned above: fixes #1198
Motivation and Context
How Has This Been Tested?
I added four test cases which test the behavior of the dirty flag in
/src/GitVersionCore.Tests/IntegrationTests/OtherScenarios.cs
.It should be set when there's any non-ignored change vs the HEAD of the repo (that includes staged files).
Other than that I had to change a some other test cases which work on the outputed data to make them work again
Screenshots (if appropriate):
Checklist: