Add support for secret-prefix for environment handling #34
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
|
Thanks for the PR! Dealing with a few other things right now. Will review it in a few days. |
|
+1 for this would be handy 👍 |
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.
Add
secret-prefixusing the convention of{secret-prefix}/{secret-name}to ensure that subsequent actions in the workflow can use the secret environment variable uniformly disregarding the environment name.@abhilash1in, as I'm not sure if this addition is in line with what you plan for the action, I created this in my fork so I can use it in my workflow. That's why I have used my name in some of the README examples. Let me know if you agree with this feature and I'll change the modifications there back.