Skip to content
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

Allow develop branch name to be configured #306

Closed
wants to merge 2 commits into from

Conversation

JakeGinnivan
Copy link
Contributor

Fixes #292

@JakeGinnivan JakeGinnivan changed the title Allow develop branch name to be configured. Fixes #292 Allow develop branch name to be configured Nov 17, 2014
@gep13
Copy link
Member

gep13 commented Nov 17, 2014

@JakeGinnivan can you fix up this log message as well:

https://github.com/ParticularLabs/GitVersion/blob/master/GitVersionCore/GitFlow/BranchFinders/DevelopBasedVersionFinderBase.cs#L69

This will be incorrect if someone chooses to alter the configuration.

Assert.IsTrue(new MockBranch("develop").IsDevelop());
Assert.IsTrue(new MockBranch("Develop").IsDevelop());
Assert.IsFalse(new MockBranch("hotfix1").IsDevelop());
Assert.IsTrue(new MockBranch("develop").IsDevelop(new Config()));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need another set of tests here to test when a configured name is being used for the develop branch that IsDevelop still works?

@gep13
Copy link
Member

gep13 commented Nov 17, 2014

@JakeGinnivan If we are going to do this for the develop branch, I think that it would make sense to do it for all configurable branch names, i.e. master, release, hotfix, support, etc. However, these can be done as separate PR's if you are in agreement.

@JakeGinnivan
Copy link
Contributor Author

After discussions in #292, not going to do this at the moment.

@JakeGinnivan JakeGinnivan deleted the MoreConfigChanges branch November 18, 2014 12:32
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.

support for other names for tags and develop branch
2 participants