64fc66ab48
Allow other CI checks to continue even if the circular import check fails. Circular imports are often indicative of code that needs to be restructured, but there are still places where we need to add them. This allows CI to continue, so that if CI is passing *except* for a problematic import, we can still force merge and accept a bit of technical debt to admit a useful feature. Also, this allows people to keep working while they fix their circular import issues, without being blind to CI results. - [x] update ci workflow: import-check continue-on-error: true |
||
|---|---|---|
| .. | ||
| bin | ||
| requirements | ||
| audit.yaml | ||
| bootstrap.yml | ||
| build-containers.yml | ||
| ci.yaml | ||
| coverage.yml | ||
| import-check.yaml | ||
| nightly-win-builds.yml | ||
| prechecks.yml | ||
| sync-packages.yaml | ||
| unit_tests.yaml | ||