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).
This commit is contained in:
Tobias Brunner 2022-04-19 16:56:06 +02:00
parent 7df710095e
commit 312437bf6a

View File

@ -31,7 +31,7 @@ jobs:
- env: - env:
LGTM_TOKEN: ${{ secrets.LGTM_TOKEN }} LGTM_TOKEN: ${{ secrets.LGTM_TOKEN }}
LGTM_PROJECT: ${{ secrets.LGTM_PROJECT }} LGTM_PROJECT: ${{ secrets.LGTM_PROJECT }}
BUILD_NUMBER: ${{ github.run_id }} BUILD_NUMBER: ${{ github.run_number }}
COMMIT_ID: ${{ github.sha }} COMMIT_ID: ${{ github.sha }}
COMMIT_BASE: ${{ github.event.before }} COMMIT_BASE: ${{ github.event.before }}
uses: ./.github/actions/default uses: ./.github/actions/default