Re: [PATCH v2] ci: allow per-branch config for GitHub Actions

From

Jeff King <peff@peff.net>

Date

May 8, 2020, 18:00 UTC

Message-ID

<20200508180047.GD637136@coredump.intra.peff.net>

In-Reply-To

<xmqqo8qz2yrr.fsf@gitster.c.googlers.com>

On Thu, May 07, 2020 at 02:58:16PM -0700, Junio C Hamano wrote:

> In any case, I'll queue it on 'pu'.  Thanks.

diff --git a/ci/config/allow-refs.sample b/ci/config/allow-ref.sample
similarity index 93%
rename from ci/config/allow-refs.sample
rename to ci/config/allow-ref.sample
index f157f1945a..c9c9aea9ff 100755
--- a/ci/config/allow-refs.sample
+++ b/ci/config/allow-ref.sample
@@ -7,8 +7,8 @@
 # your repository:
 #
 #   git checkout -b ci-config
-#   cp allow-refs.sample allow-refs
-#   $EDITOR allow-refs
+#   cp allow-refs.sample allow-ref
+#   $EDITOR allow-ref
 #   git commit -am "implement my ci preferences"
 #   git push
 #

> Perhaps we can experiment with "echo >&2 we are getting called" in
> the allow-ref script itself ;-).

That definitely ends up in the log. But doing:

  echo     "::error file=foo.sh,line=1,col=2::this is the stdout msg"
  echo >&2 "::error file=foo.sh,line=1,col=2::this is the stderr msg"

shows both versions formatted in red, which implies to me that stdout
and stderr are treated the same.

-Peff