There has been an issue with open source contributors being able to perform CI runs for their PRs - this is related to the addition of the pro checkout/submodule recursion in a recent update. Changing it to not use the contributors personal access token, but to instead use the github access token so that it can always be checked out and tested again the specified pro version.

This commit is contained in:
Michael Drury 2023-06-01 14:10:07 +01:00
parent bdc03e12cc
commit ec67b162b8
1 changed files with 6 additions and 7 deletions

View File

@ -16,7 +16,6 @@ on:
env:
BRANCH: ${{ github.event.pull_request.head.ref }}
BASE_BRANCH: ${{ github.event.pull_request.base.ref}}
PERSONAL_ACCESS_TOKEN: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
jobs:
lint:
@ -37,7 +36,7 @@ jobs:
- uses: actions/checkout@v3
with:
submodules: true
token: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
token: ${{ secrets.GITHUB_TOKEN }}
- name: Use Node.js 14.x
uses: actions/setup-node@v3
with:
@ -55,7 +54,7 @@ jobs:
- uses: actions/checkout@v3
with:
submodules: true
token: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
token: ${{ secrets.GITHUB_TOKEN }}
- name: Use Node.js 14.x
uses: actions/setup-node@v3
with:
@ -75,7 +74,7 @@ jobs:
- uses: actions/checkout@v3
with:
submodules: true
token: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
token: ${{ secrets.GITHUB_TOKEN }}
- name: Use Node.js 14.x
uses: actions/setup-node@v3
with:
@ -95,7 +94,7 @@ jobs:
- uses: actions/checkout@v3
with:
submodules: true
token: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
token: ${{ secrets.GITHUB_TOKEN }}
- name: Use Node.js 14.x
uses: actions/setup-node@v3
with:
@ -110,7 +109,7 @@ jobs:
- uses: actions/checkout@v3
with:
submodules: true
token: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
token: ${{ secrets.GITHUB_TOKEN }}
- name: Use Node.js 14.x
uses: actions/setup-node@v3
with:
@ -134,7 +133,7 @@ jobs:
uses: actions/checkout@v3
with:
submodules: true
token: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
token: ${{ secrets.GITHUB_TOKEN }}
fetch-depth: 0
- name: Check submodule
run: |