We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@maurolacy cloned issue babylonchain/babylon-contract#120 on 2024-05-29:
As part of CI checks, let's validate that: Schemas are up-to-date. (fail CI if not) Protobuf generated files are up-to-date. (fail CI if not) Git submodules don't have recent commits in their branch. (print a warning if so, do not fail CI)
As part of CI checks, let's validate that:
Schemas are up-to-date. (fail CI if not)
Protobuf generated files are up-to-date. (fail CI if not)
Git submodules don't have recent commits in their branch. (print a warning if so, do not fail CI)
The text was updated successfully, but these errors were encountered:
@bap2pecs commented on 2024-06-10:
should we also check cargo run-script lint in CI?
cargo run-script lint
Sorry, something went wrong.
No branches or pull requests
@maurolacy cloned issue babylonchain/babylon-contract#120 on 2024-05-29:
The text was updated successfully, but these errors were encountered: