Fix paths for chain configuration file copying #1890
Closed
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
Updated file paths for copying chain configuration files.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fix paths for chain configuration file copying
Description
Updated file paths for copying chain configuration files from
../deployer/to../../deployer/to reflect the correct relative path from the current working directory.Changes
rollup.jsoncopy path:../deployer/.deployer/rollup.json→../../deployer/.deployer/rollup.jsongenesis.jsoncopy path:../deployer/.deployer/genesis.json→../../deployer/.deployer/genesis.jsongenesis-l2.json)Tests
Manual verification that the updated paths correctly reference the deployer configuration files from the expected directory structure.
Additional context
The previous paths assumed a different directory structure. This fix ensures the copy commands work correctly when executed from the appropriate location in the project hierarchy.
Metadata
N/A