Remove duplicated coinbase CDP options in .env.example#863
Merged
Conversation
The removed section is identical to the section above it.
jkbrooks
approved these changes
Dec 6, 2024
dsldsl
pushed a commit
to dsldsl/eliza
that referenced
this pull request
Dec 7, 2024
Remove duplicated coinbase CDP options in .env.example
lalalune
pushed a commit
that referenced
this pull request
May 3, 2026
Remove duplicated coinbase CDP options in .env.example
FranceFlapjack
pushed a commit
to FranceFlapjack/eliza
that referenced
this pull request
May 16, 2026
Remove duplicated coinbase CDP options in .env.example
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
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.
The removed section is identical to the section above it.
Relates to:
Risks
Low
Background
What does this PR do?
It removes a duplicated section in the
.env.examplefile.What kind of change is this?
Bug fixes (non-breaking change which fixes an issue)
Why are we doing this? Any context or related work?
I believe the duplicated section is a bug. If the two sections are set to different values, it could really confuse people.
Documentation changes needed?
My changes do not require a change to the project documentation.
Testing
Where should a reviewer start?
Simple change to the example configuration.
Detailed testing steps
None, automated tests are fine.
Discord username
juntaoyuan