Skip to content
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

order of include[] in ini file matters #375

Open
halmos opened this issue Nov 18, 2019 · 0 comments
Open

order of include[] in ini file matters #375

halmos opened this issue Nov 18, 2019 · 0 comments

Comments

@halmos
Copy link

halmos commented Nov 18, 2019

Thank you for you hard work on this project.
I've been having a minor issue in that the order of a include[] seems to make a difference for condition includes. For example, an .ini file with:

include[] = 'path_a:composer.lock'
include[] = 'path_b'

will not include path_b in the deployment. However the reverse does work:

include[] = 'path_b'
include[] = 'path_a:composer.lock'

I'm not certain what the exact issue is, but it appears that a conditional include must be listed after the non-conditional include

thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant