Added 'GitVersion init' command which creates a sample GitVersionConfig....

[JakeGinnivan]

...yaml file. Fixes #305

Looks like this:

# assembly-versioning-scheme: MajorMinorPatchMetadata | MajorMinorPatch | MajorMinor | Major
# develop-branch-tag: alpha
# release-branch-tag: rc
# tag-prefix: '[vV|version-] # regex to match git tag prefix
# next-version: 1.0.0

[JakeGinnivan]

@SimonCropp I have changed assemblyVersioningScheme to assembly-versioning-scheme to line up with the other naming. Is this going to be an issue

[SimonCropp]

perhaps throw for the old invalid setting for a few versions?

[JakeGinnivan]

@SimonCropp auto upgrade that property and log warning.

https://github.com/ParticularLabs/GitVersion/pull/320/files#diff-240efcc9f8b3f9f68f3612c50d2410eaR18

Should be good to go

[SimonCropp]

Cool looks good

[gep13]

@JakeGinnivan out of interest, is there a reason that me are not seeing a TeamCity build output message here to say whether the Pull Request built correctly or not?

[JakeGinnivan]

Assume @andreasohlund changed his password or enabled 2fa :) Probably needs to use a build account.

[gep13]

Assume @andreasohlund changed his password or enabled 2fa :) Probably needs to use a build account.

Ah, that would do it :-) Who do we need to talk to to get a build account set up? @andreasohlund @SimonCropp

[gep13]

@JakeGinnivan TeamCity build status is now being reported back to GitHub @andreasohlund fixed it.