spack/.github
Harmen Stoppels 64fc66ab48
ci: import-check continue-on-error: true (#50581)
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
2025-05-20 15:50:14 -06:00
..
ISSUE_TEMPLATE Issue Templates: improve details formatting (#36923) 2023-04-14 12:16:22 -05:00
workflows ci: import-check continue-on-error: true (#50581) 2025-05-20 15:50:14 -06:00
CODE_OF_CONDUCT.md meta: move CODE_OF_CONDUCT.md and CONTRIBUTING.md to .github 2019-06-30 23:08:33 -07:00
CONTRIBUTING.md meta: move CODE_OF_CONDUCT.md and CONTRIBUTING.md to .github 2019-06-30 23:08:33 -07:00
dependabot.yml Avoid duplicate dependabot bumps (#45590) 2024-08-06 07:14:55 +00:00
pull_request_template.md Add a PR template with a reference to spackbot commands (#42349) 2024-01-30 09:43:04 +01:00