Skip to content

Commit b6eff37

Browse files
Checkout correct commit on pull_request in CI
By default, the `pull_request` event has a `GITHUB_SHA` env variable set to the "last merge commit on the GITHUB_REF branch" (see https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request). But we want to check out the latest commit on the branch whether or not it is a merge commit. This commit changes the CI actions to do just that.
1 parent 2073200 commit b6eff37

File tree

2 files changed

+16
-0
lines changed

2 files changed

+16
-0
lines changed

.github/workflows/bench.yml

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -57,6 +57,14 @@ jobs:
5757

5858
steps:
5959
- uses: actions/checkout@v3
60+
with:
61+
62+
# By default, the `pull_request` event has a `GITHUB_SHA` env variable
63+
# set to the "last merge commit on the GITHUB_REF branch" (see
64+
# https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request).
65+
# But we want to check out the latest commit on the branch whether or
66+
# not it is a merge commit, so this is how we do that.
67+
ref: "${{ github.event.pull_request.head.sha }}"
6068

6169
- run: git fetch origin master # check the master branch for benchmarking
6270

.github/workflows/flags.yml

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -55,6 +55,14 @@ jobs:
5555

5656
steps:
5757
- uses: actions/checkout@v3
58+
with:
59+
60+
# By default, the `pull_request` event has a `GITHUB_SHA` env variable
61+
# set to the "last merge commit on the GITHUB_REF branch" (see
62+
# https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request).
63+
# But we want to check out the latest commit on the branch whether or
64+
# not it is a merge commit, so this is how we do that.
65+
ref: "${{ github.event.pull_request.head.sha }}"
5866

5967
- uses: ./.github/actions/setup-build
6068
with:

0 commit comments

Comments
 (0)