ci: avoid using the deprecated `set-env` construct
The `set-env` construct was deprecated as of the announcement in https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ Let's use the recommended alternative instead. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Johannes Schindelin committed
Nov 7, 2020 at 01:21 UTC
cac42e471afae5b1af4f0745388981675b920d91
1 file changed
+1
-1
.github/workflows/check-whitespace.yml
+1
-1
index 9d070b9cdf..c74b47de9e 100644
--- a/.github/workflows/check-whitespace.yml
+++ b/.github/workflows/check-whitespace.yml
@@ -14,7 +14,7 @@ jobs:
steps:
- name: Set commit count
shell: bash
- run: echo "::set-env name=COMMIT_DEPTH::$((1+$COMMITS))"
+ run: echo "COMMIT_DEPTH=$((1+$COMMITS))" >>$GITHUB_ENV
env:
COMMITS: ${{ github.event.pull_request.commits }}