From: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: [PATCH 0/2] ci: avoid ugly "failure" annotation in the GitHub workflow
Date: Tue, 01 Sep 2020 20:19:25 +0000 [thread overview]
Message-ID: <pull.719.git.1598991568.gitgitgadget@gmail.com> (raw)
Whenever the GitHub workflow runs in a fork that does not contain the
special-purpose ci-config branch, a big fat failure annotation greets the
casual reader. See e.g.
https://github.com/gitgitgadget/git/actions/runs/233438295
This is caused by the (non-fatal) failure to clone said branch. Let's avoid
that. It's distracting.
Johannes Schindelin (2):
ci: fix indentation of the `ci-config` job
ci: avoid ugly "failure" in the `ci-config` job
.github/workflows/main.yml | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
base-commit: e19713638985533ce461db072b49112da5bd2042
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-719%2Fdscho%2Favoid-error-in-ci-config-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-719/dscho/avoid-error-in-ci-config-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/719
--
gitgitgadget
next reply other threads:[~2020-09-01 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 20:19 Johannes Schindelin via GitGitGadget [this message]
2020-09-01 20:19 ` [PATCH 1/2] ci: fix indentation of the `ci-config` job Johannes Schindelin via GitGitGadget
2020-09-02 0:33 ` Jeff King
2020-09-01 20:19 ` [PATCH 2/2] ci: avoid ugly "failure" in " Johannes Schindelin via GitGitGadget
2020-09-02 0:40 ` Jeff King
2020-09-02 19:21 ` [PATCH 0/2] ci: avoid ugly "failure" annotation in the GitHub workflow Junio C Hamano
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pull.719.git.1598991568.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 NNTP newsgroup(s).