JETS_EXTRA support, deprecate JETS_ENV_EXTRA #643
Merged
Conversation
This file contains hidden or 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
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.
This is a 🙋♂️ feature or enhancement.
bundle exec rspecto verify this)Summary
Use
JETS_EXTRAinstead ofJETS_ENV_EXTRAfor https://rubyonjets.com/docs/env-extra/ concept. Other boltops tooling use this shorter naming convention also.Note:
JETS_ENV_EXTRAis still supported so it doesn't break people's pipeline. A deprecation warning is shown.The docs PR will follow.
How to Test
Deploy with:
Version Changes
Minor