From 73944645aa90e2193bb4139a4249d47e63c1f534 Mon Sep 17 00:00:00 2001 From: flip1995 Date: Tue, 1 Mar 2022 10:10:01 +0000 Subject: [PATCH] Move testing of cargo dev new_lint to cargo dev workflow This should be placed there. No need to run this in PR CI, if clippy_dev isn't touched. (It will be run by bors anyway) --- .github/workflows/clippy.yml | 7 ------- .github/workflows/clippy_bors.yml | 7 ------- .github/workflows/clippy_dev.yml | 7 +++++++ 3 files changed, 7 insertions(+), 14 deletions(-) diff --git a/.github/workflows/clippy.yml b/.github/workflows/clippy.yml index 116ae031bb719..cd83bc9642b60 100644 --- a/.github/workflows/clippy.yml +++ b/.github/workflows/clippy.yml @@ -74,10 +74,3 @@ jobs: run: bash .github/driver.sh env: OS: ${{ runner.os }} - - - name: Test cargo dev new lint - run: | - cargo dev new_lint --name new_early_pass --pass early - cargo dev new_lint --name new_late_pass --pass late - cargo check - git reset --hard HEAD diff --git a/.github/workflows/clippy_bors.yml b/.github/workflows/clippy_bors.yml index 989667037c1cb..f571485e6d389 100644 --- a/.github/workflows/clippy_bors.yml +++ b/.github/workflows/clippy_bors.yml @@ -143,13 +143,6 @@ jobs: env: OS: ${{ runner.os }} - - name: Test cargo dev new lint - run: | - cargo dev new_lint --name new_early_pass --pass early - cargo dev new_lint --name new_late_pass --pass late - cargo check - git reset --hard HEAD - integration_build: needs: changelog runs-on: ubuntu-latest diff --git a/.github/workflows/clippy_dev.yml b/.github/workflows/clippy_dev.yml index fe8bce00fa82e..5dfab1d2ebc40 100644 --- a/.github/workflows/clippy_dev.yml +++ b/.github/workflows/clippy_dev.yml @@ -36,6 +36,13 @@ jobs: - name: Test fmt run: cargo dev fmt --check + - name: Test cargo dev new lint + run: | + cargo dev new_lint --name new_early_pass --pass early + cargo dev new_lint --name new_late_pass --pass late + cargo check + git reset --hard HEAD + # These jobs doesn't actually test anything, but they're only used to tell # bors the build completed, as there is no practical way to detect when a # workflow is successful listening to webhooks only.