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

Prompt user if extant .env file would be overwritten by running env-init #166

Merged
merged 3 commits into from
Jun 20, 2020
Merged

Conversation

Lunaetic
Copy link
Contributor

@Lunaetic Lunaetic commented Jun 18, 2020

PR replaces a TODO: with bash scripting that prompts the user to confirm that .env should be overwritten.

Testing

  • Pull PR
  • Create a new, empty directory, and from that directory, run warden env-init test magento2; assert that the .env file is created as normal
  • Make a change to the .env file
  • Run warden env-init test magento2 again; when prompted, answer n; assert that the change you made previously is still in the file
  • Run warden env-init test magento2 again; when prompted, answer y; assert that the change you made previously is no longer there
  • Run warden env-init test magento2 again; when prompted, answer anything other than y or n; assert that you are asked to provide a valid answer

@davidalger davidalger added the enhancement New feature or request label Jun 19, 2020
@davidalger davidalger added this to the Warden 0.6.0 milestone Jun 19, 2020
davidalger added a commit that referenced this pull request Jun 20, 2020
@davidalger davidalger merged commit 7dd2075 into wardenenv:develop Jun 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants