Record historic values #18
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…w value on new line. Include timecode when it was changed.
… commented out keys with a matching value. This is important so we don't destroy the datetimes in the previously commented values and also it fixes a bug with random line breaks in the env file.
# Conflicts: # src/EnvironmentSetCommand.php
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Succeeds #14 (thanks @bottlenosecreative for the original PR)
With the environment variable
ENVSET_HISTORYset totrue, theenv:setcommand will record any changes you make to your .env file by leaving a comment containing the old value and the date it was changed.