This repository was archived by the owner on Sep 26, 2025. It is now read-only.
Event triggers can also use ENV vars for their headers #14
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
This PR adds support to those
endpoint Creates .env.development even if no env vars are fetched
This was referenced Apr 17, 2020
Contributor
|
Awesome! Release time! :D |
nunopato
force-pushed
the
add-support-for-env-vars-headers
branch
from
df5c252 to
8d0b28f
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
--endpoint(fixes apply migrations on remote server right after nhost init with --skip-execution #17)