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
It doesn't leverage the already configured tox test environments
It uses different tools for linting (hence, testing locally with tox can produce different results)
It leaves out a big part of the code, namely all tests
Goal
Configure the lint CI action to use tox, making sure that both the top-level (e.g. tests) and charm-specific (e.g. charms/katib-controller/tests) directories are checked.
The text was updated successfully, but these errors were encountered:
Currently, our CI workflow manually configures a
lint
action to check the charm code:katib-operators/.github/workflows/integrate.yaml
Lines 24 to 43 in a9c7609
This is unfortunate for a few reasons:
Goal
Configure the
lint
CI action to usetox
, making sure that both the top-level (e.g.tests
) and charm-specific (e.g.charms/katib-controller/tests
) directories are checked.The text was updated successfully, but these errors were encountered: