use explicit repo location for boostd-data #1748
Merged
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
LexLuthr
approved these changes
Oct 11, 2023
nonsense
force-pushed
the
nonsense/explicit-repo-for-boostd-data
branch
from
1167f18 to
8dbe9c2
Compare
nonsense
force-pushed
the
nonsense/explicit-repo-for-boostd-data
branch
from
8dbe9c2 to
3c8ba5b
Compare
nonsense
added a commit
that referenced
this pull request
Oct 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
At the moment it is confusing that we are re-using the boostd repo for boostd-data, so this PR is changing this, in order to be explicit we are actually running a different process in the devnet.