You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should verify that the example repo is and remains valid and this
also serves as a useful test with a more complex repo.
This should resolvescience-computing#23 (we already have such an example packages repo
in this butido Git repo and this test does at least verify that it can
be loaded, i.e., that the definitions are syntactically valid (regarding
the type checking) - ideally we'd also have a high-level test that
actually runs some builds to verify the logic (semantics) but that can
be done as part of science-computing#109 / the CLI tests in science-computing#43).
Signed-off-by: Michael Weiss <[email protected]>
ammernico
pushed a commit
to ammernico/butido
that referenced
this issue
Apr 30, 2024
We should verify that the example repo is and remains valid and this
also serves as a useful test with a more complex repo.
This should resolvescience-computing#23 (we already have such an example packages repo
in this butido Git repo and this test does at least verify that it can
be loaded, i.e., that the definitions are syntactically valid (regarding
the type checking) - ideally we'd also have a high-level test that
actually runs some builds to verify the logic (semantics) but that can
be done as part of science-computing#109 / the CLI tests in science-computing#43).
Signed-off-by: Michael Weiss <[email protected]>
Stop ignoringLint with the beta toolchain as well (but only make the results with the MSRV binding): actions: Run optional clippy (linting) checks with the beta toolchain #111cargo clippy
warningsrustfmt
) via CI: Format the codebase via rustfmt #263The text was updated successfully, but these errors were encountered: