Merge multiple configuration files

[akritikos]

Given the new release that supports multiple versions on the same repository, would you consider handing configuration values in a fashion similar to Directory.Build.props by msbuild? That is, merge files in the parent folders, with the current directory overriding all parents.

That way, we could maintain a centralized configuration for branches & deployment modes, while being able to override items such as ignore-paths & tag-prefix. An alternative solution would be to add ignore-paths as an available key for overrideconfig.

[asbjornu]

Since people may already have several GitVersion configuration files, I think we need to do this with an opt-in flag of some sort to not break anything. Alternatively, we postpone this feature to v7. Thoughts?

[akritikos]

That seems like a reasonable way to tackle this!

[asbjornu]

Which of the options do you prefer? We have no planned release date for v7, so it might take a while for this feature to become available if we postpone it. Perhaps we can introduce it under a flag in v6? Would you be up for implementing this feature and submit a PR?

[akritikos]

I'd personally go for configuration files, to avoid passing an increasing amount of arguments! I can get started on an implementation by the end of the month