This repository has been archived by the owner on Feb 13, 2023. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 645
.gitignore errors in latest version #1411
Labels
Comments
oxyc
added a commit
to oxyc/drupal-vm
that referenced
this issue
Jun 6, 2017
Technically this is how I originally intended it to work, but I see your point. For applications like BLT, the But it should probably only be excluded in the root directory (for testing or using Drupal VM completely standalone), not in subdirectories. It looks like @oxyc is working on a fix already 😀 |
Just trying to find the git version when leading / was added 😄 |
oxyc
added a commit
to oxyc/drupal-vm
that referenced
this issue
Jun 6, 2017
Thanks for the update and great tool, BTW! |
geerlingguy
added a commit
that referenced
this issue
Jun 28, 2017
Issue #1411: Fix gitignore applying rules to files in subdirectories
That change has been merged in, so it will be part of the next minor release... which I hope to push out this week (was going for the weekend, but life got in the way, so it'll be sometime this week). |
ashabed
pushed a commit
to debugacademy/academyvm
that referenced
this issue
Jan 18, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue Type
Your Environment
NOTE: I'm running ansible through the GUEST via the
force_ansible_local: true
setting.Your OS
Full console output
https://gist.github.com/inversed/b469c0e64709b2828f95b735a81aa8b4
Summary
Drupal-VM's .gitignore excludes a required file (provisioning/tasks/config.yml).
When trying to do a
vagrant up
on a project where Drupal-VM itself has been included in a repo, that file (andtests/config.yml
) is missing so the spin up operation fails.This might not be the intended use case (docs specify running this Windows 10's Bash) but this approach does work fine. Seems like this is a minor bug that's easy to fix but I don't know if it's actually an intentional configuration issue.
The text was updated successfully, but these errors were encountered: