Skip to content

[Configuration Bugfix] source-branches is overwritten even if explicitly specified in the config #1590

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

ruhullahshah
Copy link
Contributor

@ruhullahshah ruhullahshah commented Feb 18, 2019

Problem:

Adding source-branches to the config has no effect and is always overwritten with the default values.

Steps to Reproduce:

Add source-branches: ['develop'] to the develop branch configuration and upon running GitVersion.exe /showconfig the source-branches: [] will be displayed.

Cause:

SourceBranches from BranchConfig was not being checked before applying the defaults.

Fix:

Check SourceBranches before applying the defaults.

The reason for creating the fix from the tip of 4.0.0 is that, we expect it to get merged into a support/4.0.x branch, providing an alternative for the users who do not want to upgrade to 5.0.0 yet.

Ruh Ullah Shah and others added 4 commits February 18, 2019 14:08
Problem: Adding source-branches to the config had no effect and would
always be over-written with the
default value specified in the configuration provider for the default
branches.
Cause: SourceBranches from BranchConfig was not being checked before
being over-written.
Fix: Check SourceBranches and use it before applying the defaults.
@arturcic arturcic requested a review from asbjornu February 19, 2019 12:35
@asbjornu asbjornu merged commit 371a896 into GitTools:master Feb 19, 2019
@arturcic arturcic added this to the 5.0.0 milestone Feb 19, 2019
@ruhullahshah ruhullahshah deleted the bugfix/source_branches_specified_in_config_should_not_be_overwritten branch February 20, 2019 13:26
@arturcic arturcic added the Bug label Mar 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants