From 977b0da0ab2ff45165e0f842fc4de936ee529c78 Mon Sep 17 00:00:00 2001 From: Luke Parker Date: Tue, 15 Nov 2022 08:07:25 -0500 Subject: [PATCH] Clarify reasoning for not checking advisories in CI --- .github/workflows/tests.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/workflows/tests.yml b/.github/workflows/tests.yml index 7ab50b8fe..8452d6069 100644 --- a/.github/workflows/tests.yml +++ b/.github/workflows/tests.yml @@ -50,8 +50,9 @@ jobs: # Doesn't run on advisores due to their frequency and general irrelevancy # The official recommendation is to continue when they fail, yet you can't # even open an issue when they do, making it pointless to have here + # GitHub will still alert us if an advisory appears - name: Run cargo deny - run: cargo deny -L error --all-features check bans licenses sources + run: cargo deny -L error --all-features check licenses bans sources test: runs-on: ubuntu-latest