Add config file support to GitVersionTask

[SimonCropp]

If a file named GitVersionConfig.yaml is detected in the root git directory then settings will be read from that file.

Currently the only property supported is assemblyVersioningScheme which can be one of

• MajorMinorPatch
• MajorMinor
• Major

So for example

assemblyVersioningScheme: Major

[distantcam]

Instead of having yet another config file in the root, could we use the AssemblyInfo.cs somehow to determine this?

[SimonCropp]

@distantcam "yet another config file in the root" versus "duplicating the config in multiple cs files"

[distantcam]

Ok. Maybe we could drop the NextVersion.txt file and merge it with GitVersionConfig.yaml?

[SimonCropp]

Maybe we could drop the NextVersion.txt file and merge it with GitVersionConfig.yaml?

+1 i will work on this

[andreasohlund]

+1

On Fri, Sep 26, 2014 at 9:14 AM, Simon Cropp notifications@github.com
wrote:

Maybe we could drop the NextVersion.txt file and merge it with
GitVersionConfig.yaml?

+1 i will work on this

—
Reply to this email directly or view it on GitHub
#256 (comment)
.

[robdmoore]

+1, but it would be nice if it either kept using nextversion.txt if it's there and output a warning or throw an error so that existing repos will still work.

On 26 Sep 2014, at 3:57 pm, Andreas Öhlund notifications@github.com wrote:

+1

On Fri, Sep 26, 2014 at 9:14 AM, Simon Cropp notifications@github.com
wrote:

Maybe we could drop the NextVersion.txt file and merge it with
GitVersionConfig.yaml?

+1 i will work on this

—
Reply to this email directly or view it on GitHub
#256 (comment)
.

—
Reply to this email directly or view it on GitHub.

[JakeGinnivan]

Also should allow specifying the config file, and all settings should be under a GitVersion header. That way the GitVersion config can be merged with other yaml config files

[gep13]

Also should allow specifying the config file, and all settings should be under a GitVersion header. That way the GitVersion config can be merged with other yaml config files

I think this is a great idea!

[distantcam]

Also should allow specifying the config file, and all settings should be under a GitVersion header. That way the GitVersion config can be merged with other yaml config files

How do we specify which config file to use?

Why not also use xml for config so we can include the config in an xml file like the resharper settings file for example?

Could we also include the config as part of the .sln file?

[SimonCropp]

ok closing this since technically it work for GitVersionTask which is the intent. can u guys raise other issues for the various bits