Feature: VM configuration non-tracked and add template file #114
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
While at it, extend ignore rule for /disks to cover any deeper structure (it is the case for Parallels provider disks)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When doing development for this project (or following changes in downstream projects) it is cumbersome to have the
vm.ymlfile being tracked in the source repository since it may generate conflicts when switching branches.Also, more importantly, people having an already customized
vm.ymlfile will have problems "fast-forwarding" their cloned project as the contents of the file is chaning in the origin repo.For these reasons I propose to have the default contents put aside as a new
vm-defaults.ymlfile that is tracked in the source repo and keepvm.ymlas an unversioned file.PS: also removed the unmaintained
default.ymlfile.