From 312437bf6a2e90dfe3eb7aedb245443010f9bbfa Mon Sep 17 00:00:00 2001 From: Tobias Brunner Date: Tue, 19 Apr 2022 16:56:06 +0200 Subject: [PATCH] github: Use run_number instead run_id as external-id for LGTM The external-id parameter takes an int32 and the generated run_id was apparently not valid lately, resulting in undocumented 404 errors when submitting patches (the API endpoint probably doesn't like negative numbers because the last accepted id was 2059658094, rejected ids were e.g. 2167472705 or 2168792083). --- .github/workflows/lgtm.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/lgtm.yml b/.github/workflows/lgtm.yml index 717af4711d..adc05277bd 100644 --- a/.github/workflows/lgtm.yml +++ b/.github/workflows/lgtm.yml @@ -31,7 +31,7 @@ jobs: - env: LGTM_TOKEN: ${{ secrets.LGTM_TOKEN }} LGTM_PROJECT: ${{ secrets.LGTM_PROJECT }} - BUILD_NUMBER: ${{ github.run_id }} + BUILD_NUMBER: ${{ github.run_number }} COMMIT_ID: ${{ github.sha }} COMMIT_BASE: ${{ github.event.before }} uses: ./.github/actions/default