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 creating a new project with BLT following these instructions, after the
local:setup
step I get a /files-private directory in the repo root that should be gitignored.I'm not quite sure why this directory is created in the repo root instead of in the Drupal docroot. This PR seems like it would put it into the docroot: #322 🤷♂️
Regardless, I'm definitely not seeing it at docroot/sites/*/files-private, which is where BLT apparently expects it to be following #732, so I figure we should change to the gitignore to match reality.
@dpagini under what circumstances were you seeing files show up at docroot/sites/*/files-private? I'm guessing it was for an older version of BLT?