Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
GitVersionTask 3.6.5 ignoring GitVersion.yml in project dir #1170
Given a VS solution with one or more projects that have the
The docs at http://gitversion.readthedocs.io/en/latest/configuration/ say that I should be able to put the config file in any solution subdirectory, "in case you have a single repository for more than one project" and want to set different GitVersion parameters on each.
GitVersion CLI run from the project directory behaves correctly.
Hi all, I want to share a workaround that seems to be working:
After that you might want to roll back the change or not - depending on your need. For me it seems it is nice to scope down to the only nuget package from the collection of nuget packages in our nugetPackages monorepo.
Forgive me for being confused but how does this help in versioning per project in a single git repo?
If the git version ymls in the project subfolders are honored, can i have a different version for project1 and project2?
I believe the major and minor versions are based on tagging, the patch number could be by tag or commit number and the build number is based on commits since the last tag.
How do I set this up? Do I need to have a specific format for tags to say that that tag is meant for project1?
Is it possible to setup commit count tracking by folder too?
Any further comments on this scenario? I can see how @gparlakov workaround would handle the M.M.P versions as you could control these in the gitversion config scoped per solution, but @isen-ng point is that the pre-prelease tags will still need some way to be generated per solution.
I can't see any other way of achieving this for a mono-repo setup.