-
Notifications
You must be signed in to change notification settings - Fork 654
Support for dotted versions of the GitVersion config files by default #4432
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
All suggestions applied and rebased to current main. 👍 |
follow the convention of having a leading dot for config files used e.g. for .gitignore, .editorconfig, .gitattributes, etc
44e1c7e
to
ea03747
Compare
please run |
Its the line you suggested: |
|
To make the linter happy you need to have a whitespace between the two dots |
Thank you @Bi0T1N for your contribution! |
Description
Follow the convention of many other tools which use a leading dot for their configuration files, e.g.
.gitignore
,.editorconfig
,.gitattributes
, etc.Related Issue
Closes #4431
Motivation and Context
With this change GitVersion will look for the following configuration files by default:
GitVersion.yml
,GitVersion.yaml
,.GitVersion.yml
and.GitVersion.yaml
(in this order)How Has This Been Tested?
By extending the unit tests.
Checklist: