Skip to content

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

Conversation

JakeGinnivan
Copy link
Contributor

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)

@JakeGinnivan JakeGinnivan force-pushed the ConfigBasedVersioning branch from da75d3a to e2f6a5b Compare January 11, 2015 11:30
@@ -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");
Copy link
Contributor Author

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

@JakeGinnivan JakeGinnivan force-pushed the ConfigBasedVersioning branch from e2f6a5b to 7311fd5 Compare January 11, 2015 11:50
@JakeGinnivan JakeGinnivan changed the title [WIP] Config based versioning Config based versioning Jan 11, 2015
@JakeGinnivan
Copy link
Contributor Author

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

@JakeGinnivan
Copy link
Contributor Author

Prob no point just reviewing this. Just look at #346

@JakeGinnivan JakeGinnivan deleted the ConfigBasedVersioning branch January 18, 2015 11:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant