-
Notifications
You must be signed in to change notification settings - Fork 256
Update devnet spec to mirror mainnet specs #2649
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
fe4c7bb to
ae311b4
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2649 +/- ##
===========================================
- Coverage 59.67% 18.55% -41.12%
===========================================
Files 345 3 -342
Lines 15984 97 -15887
Branches 22 22
===========================================
- Hits 9538 18 -9520
+ Misses 5705 78 -5627
+ Partials 741 1 -740 🚀 New features to boost your workflow:
|
ae311b4 to
14a8b5e
Compare
14a8b5e to
db5cba7
Compare
db5cba7 to
8efc469
Compare
b002f51 to
8efc469
Compare
8efc469 to
8511786
Compare
8511786 to
bf0d2f7
Compare
calbera
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just noting here that eventually we probably want to remove the "devnet" spec entirely and use chain-spec by file for any custom networks (including cloud devnets, local, e2e suite, etc). Until that is fully configured (and pending my PR for UX improvements), we can continue using "devnet" spec as such
cc16d7b to
fd2b6b2
Compare
fd2b6b2 to
7e86f18
Compare
7e86f18 to
5b56985
Compare
5b56985 to
af621a1
Compare
No description provided.