Skip to content

Commit 139b136

Browse files
committed
Provide ref fallback value in the check_commits CI
Previously, we introduced a chance dynamically determining the base branch for the `check_commits` CI job. Unfortunately it used the `base_ref` variable, which is only set for `pull_request`s, not for `push`es. Here, we therefore also provide a `ref_name` fallback value, which should also work for our post-merge 'push' CI.
1 parent a48d650 commit 139b136

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

.github/workflows/build.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -198,9 +198,9 @@ jobs:
198198
git fetch upstream
199199
export GIT_COMMITTER_EMAIL="[email protected]"
200200
export GIT_COMMITTER_NAME="RL CI"
201-
git rebase upstream/${{ github.base_ref }}
201+
git rebase upstream/${{ github.base_ref || github.ref_name }}
202202
- name: For each commit, run cargo check (including in fuzz)
203-
run: ci/check-each-commit.sh upstream/${{ github.base_ref }}
203+
run: ci/check-each-commit.sh upstream/${{ github.base_ref || github.ref_name }}
204204

205205
check_release:
206206
runs-on: ubuntu-latest

0 commit comments

Comments
 (0)