-
Notifications
You must be signed in to change notification settings - Fork 227
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
bug(local): Ignore env specification when it's not a file #2698
Conversation
8400161
to
7e77c20
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
~~ A small logical error prevented me from getting the warning during testing. ~~
After clarification, it is intentional that the warning will not be displayed under certain circumstances.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
7e77c20
to
caa5dc9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
caa5dc9
to
c9912b7
Compare
#2007
Description
heroku local
andheroku run
allow users to specify an env file location. If that location is a directory instead, the command fails. This adds logic to ignoreenv
file locations that are not files, and warns the user.Testing
local web
within an app's directory that has a.env
that is a directory.env
is ignored and warns the user