-
Notifications
You must be signed in to change notification settings - Fork 654
Config based versioning #344
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
Config based versioning #344
Conversation
da75d3a
to
e2f6a5b
Compare
@@ -12,7 +12,8 @@ public void WhenDevelopBranchedFromMaster_MinorIsIncreased() | |||
{ | |||
fixture.Repository.MakeATaggedCommit("1.0.0"); | |||
fixture.Repository.CreateBranch("develop").Checkout(); | |||
fixture.AssertFullSemver("1.1.0-unstable.0+0"); | |||
fixture.Repository.MakeACommit(); | |||
fixture.AssertFullSemver("1.1.0-unstable.1+0"); |
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.
develop
is inconsistent. Other tags start counting at 1, develop at 0. Making the code generic means develop now starts counting it's tag at 1
e2f6a5b
to
7311fd5
Compare
Once #343 is merged, this can be merged. I will continue development on a separate branch as it will involve changing tests and that would be good to be isolated in it's own PR |
…t kinda works but lots of small differences causing test breaks
7311fd5
to
513004a
Compare
Prob no point just reviewing this. Just look at #346 |
Start of new internals which does not use any branch finders or know anything about branches.
Still a bunch of integration tests which need to be fixed when you switch over to use new stuff in
GitVersionFinder
(uncomment commented line)