Does the "check" workflows only do stuff, that is done in the full test suite anyway ?
maybe that is a reliquary from an older parity CI Setup.
currently we do have a lot of warning, but no error, for the check test.
If we can ensure that the check workflow is useless, we can delete it and do not need to maintain it.
Does the "check" workflows only do stuff, that is done in the full test suite anyway ? maybe that is a reliquary from an older parity CI Setup.
currently we do have a lot of warning, but no error, for the
checktest. If we can ensure that the check workflow is useless, we can delete it and do not need to maintain it.