Fix CONTINUE_API_KEY usage in GitHub workflow examples #7975
+27
−6
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.
Fixes CONTINUE_API_KEY usage in GitHub workflow examples to follow best practices by using environment variable declarations instead of inline secrets references.
Changes
Before
After
This follows GitHub Actions best practices for handling secrets and environment variables.
Resolves: CON-4107
This agent session was created by tingwai and co-authored by Continue noreply@continue.dev.
Summary by cubic
Updated GitHub Actions examples to use CONTINUE_API_KEY via env instead of inline secrets. Addresses CON-4107 and aligns with GitHub Actions best practices for secrets.