-
-
Notifications
You must be signed in to change notification settings - Fork 61
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
feat: add support for multiple .env files. #683
Conversation
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.
@AkhilJ321 Please resolve the conflicts. btw, have you tested it?
@KhudaDad414 yes , I tested it through a example where npm run dev used development env and on npm run start used production env. |
@KhudaDad414 ,I am not getting what to remove, I have only removed dotenv imports and added next/env. What confict is to be resolved ,can you help me with this one |
@AkhilJ321 Conflicts happen when someone makes a change to a file that you are working on in your PR. because GitHub doesn't know which changes it should keep. what conflict is: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts |
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
@KhudaDad414 Thank you for the help, resolved the conflict. |
/rtm |
thanks for the contribution @AkhilJ321 🙇 |
@allcontributors please add @AkhilJ321 for code |
I've put up a pull request to add @AkhilJ321! 🎉 |
🎉 This PR is included in version 0.35.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
Related issue(s)
Fixes: #638