list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: "Johannes Schindelin via GitGitGadget" <>
Cc: "Chris. Webster" <>,
	Johannes Schindelin <>,
	Johannes Schindelin <>
Subject: [PATCH] ci: avoid using the deprecated `set-env` construct
Date: Sat, 07 Nov 2020 01:21:45 +0000	[thread overview]
Message-ID: <> (raw)

From: Johannes Schindelin <>

The `set-env` construct was deprecated as of the announcement in

Let's use the recommended alternative instead.

Signed-off-by: Johannes Schindelin <>
    ci: avoid using the deprecated set-env construct
    This avoids an ugly warning (see e.g. this run

Fetch-It-Via: git fetch pr-781/dscho/no-set-env-in-github-workflows-v1

 .github/workflows/check-whitespace.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/check-whitespace.yml b/.github/workflows/check-whitespace.yml
index 9d070b9cdf..c74b47de9e 100644
--- a/.github/workflows/check-whitespace.yml
+++ b/.github/workflows/check-whitespace.yml
@@ -14,7 +14,7 @@ jobs:
     - name: Set commit count
       shell: bash
-      run: echo "::set-env name=COMMIT_DEPTH::$((1+$COMMITS))"
+      run: echo "COMMIT_DEPTH=$((1+$COMMITS))" >>$GITHUB_ENV
         COMMITS: ${{ github.event.pull_request.commits }}

base-commit: 7f7ebe054af6d831b999d6c2241b9227c4e4e08d

             reply	other threads:[~2020-11-07  1:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-07  1:21 Johannes Schindelin via GitGitGadget [this message]
2020-11-07  6:51 ` Chris Webster
2020-11-17  6:19 ` Junio C Hamano
2020-11-17 15:21   ` Johannes Schindelin
2020-11-17 20:14     ` Junio C Hamano
2020-11-18 11:48       ` Johannes Schindelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: [PATCH] ci: avoid using the deprecated `set-env` construct' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).