Add env_name
to each FastlaneCore::ConfigItem
#120
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.
Hello @HazAT 👋
We've been using this action for a while and it's been doing a great job! I was recently doing some refactoring however and I want to cleanup some of our fastfiles by doing the following:
I've done this in a lot of other places by defining our default parameters in a .env file, however I found that we couldn't do it with this action because it doesn't define the
env_name
on the available options so this PR aims to address that 🙏It should be a relatively small change all things considered 🙇