Better handling of .gitkeep in demo-files #2304
Merged
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.
We use
.gitkeep
files as placeholders for "empty" directories. For example we have two demo active projects that don't contain any files, and we want theloaddemo
command to create project directories for them. However,loaddemo
(orTestMixin
, which loads the demo files for the test suite) shouldn't create an actual.gitkeep
file in the project directory.Additionally,
loaddemo
shouldn't fail if the demo project directory already exists.Should fix problems with
test-upgrade.sh
as seen in #2303.