-
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
invalid use of Lazy<GitVersionContext>, #2933 fix doesn't work actualy #2951
Conversation
Could you please rebase this on |
Please go on |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not comfortable not having tests that exercise the failure you've experienced, but since no existing tests fail, I suppose this should be fine.
Thank you @hyabean for your contribution! |
🎉 This issue has been resolved in version 5.9.0 🎉 Your GitReleaseManager bot 📦🚀 |
Description
Fixes #2927
Related Issue
#2927
Motivation and Context
Invalid use of Lazy leads the fix of #2933 doesn't work properly. this.versionContext.Value will always be null. This problem was bypassed by way of early access in unit test.
if replace
with
bool isCurrentCommitTagged = context.IsCurrentCommitTagged;
,will cause many other unit tests failed.
So I have to move the if statement into the NormalizeGitDirectory method.
How Has This Been Tested?
Tested the reproduce case in #2927.
all unit tests passed
Screenshots (if appropriate):