enhance: add support for gptscript.env file in workspace #554
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
thedadams
approved these changes
Jun 26, 2024
njhale
approved these changes
Jun 26, 2024
To add environment variables to a sys.exec call, the user can populate a gptscript.env file with a list of environment variables per line in the format: ``` FOO=bar ``` This file can be precreated or modified by gptscripts. Signed-off-by: Bill Maxwell <cloudnautique@users.noreply.github.com>
cloudnautique
force-pushed
the
add_envfile_support
branch
from
853b0a0 to
f1c0282
Compare
thedadams
approved these changes
Jun 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
To add environment variables to a sys.exec call, the user can populate a gptscript.env file with a list of environment variables per line in the format:
This file can be precreated or modified by gptscripts.