feat: next vote testing with core integration tests #373
+1,090
−14
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
Move script and test to the archive
fix: count all exited validators in each module
[HOLESKY] Change the limits & period for ET for LOL
tamtamchik
force-pushed
the
feat/next-vote-with-core
branch
2 times, most recently
from
ee12925 to
d467b73
Compare
tamtamchik
force-pushed
the
feat/next-vote-with-core
branch
from
d467b73 to
f63ad7f
Compare
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.
This is a special PR for testing CI setup running
feat/next-votebranch against core integration tests.