-
Notifications
You must be signed in to change notification settings - Fork 394
Pass --dir to @netlify/config #1010
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
Conversation
src/commands/deploy.js
Outdated
if (flags['dir']) { | ||
deployFolder = path.resolve(process.cwd(), flags['dir']) | ||
} else if (get(config, 'build.publish')) { | ||
if (get(config, 'build.publish')) { | ||
deployFolder = path.resolve(site.root, get(config, 'build.publish')) | ||
} else if (get(siteData, 'build_settings.dir')) { |
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.
config.build.publish
includes siteData.build_settings.dir
, so this branch should not be needed anymore.
Co-authored-by: ehmicky <[email protected]>
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.
Should we add several automated tests to cover this change?
To make sure netlify deploy
is not using the wrong publish directory, as this would bring down users websites. What do you think?
Closing due to inactivity |
- Summary
Fixes #961
- Test plan
- Description for the changelog
--dir
flag to@netlify/config
build.publish
instead of--dir
flag innetlify deploy
andnetlify dev
- A picture of a cute animal (not mandatory but encouraged)
🐬