chore: update env for plugin-goat #1180
Merged
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
odilitime
previously approved these changes
Dec 17, 2024
odilitime
changed the title
Where? |
|
search the repo for any mention of ALCHEMY_API_KEY if none, at a bare minimum include the instructions of the plugin README |
Codecov ReportAll modified and coverable lines are covered by tests ✅ |
aeither
force-pushed
the
update-env-plugin-goat
branch
from
82be6fb to
df9f57f
Compare
1to3for5vi7ate9x
pushed a commit
to 1to3for5vi7ate9x/eliza
that referenced
this pull request
Jan 26, 2025
chore: update env for plugin-goat
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.
Relates to:
Risks
Background
What does this PR do?
Update ALCHEMY_API_KEY to EVM_PROVIDER_URL for plugin-goat
which is more accurate as user can provide any rpc URL. it is not an alchemy api key what needs to be provided
What kind of change is this?
Documentation changes needed?
Testing
Where should a reviewer start?
Detailed testing steps