From: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Johannes Schindelin <johannes.schindelin@gmx.de>,
Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: [PATCH 1/2] ci: fix indentation of the `ci-config` job
Date: Tue, 01 Sep 2020 20:19:26 +0000 [thread overview]
Message-ID: <b5363e282f69570e34ffb806f7a62e00e39b98bc.1598991568.git.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.719.git.1598991568.gitgitgadget@gmail.com>
From: Johannes Schindelin <johannes.schindelin@gmx.de>
The section added in e76eec35540f (ci: allow per-branch config for
GitHub Actions, 2020-05-07) contains a `&&`-chain that connects several
commands. The first command is actually so long that it stretches over
multiple lines, and as per usual, the continuation lines are indented one
more level than the first.
However, the subsequent commands in the `&&`-chain were also indented
one more level than the first command, which was almost certainly
unintended.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
---
.github/workflows/main.yml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
index 30425404eb..6fd1d1a2c8 100644
--- a/.github/workflows/main.yml
+++ b/.github/workflows/main.yml
@@ -23,8 +23,8 @@ jobs:
--filter=blob:none \
https://github.com/${{ github.repository }} \
config-repo &&
- cd config-repo &&
- git checkout HEAD -- ci/config
+ cd config-repo &&
+ git checkout HEAD -- ci/config
- id: check-ref
name: check whether CI is enabled for ref
run: |
--
gitgitgadget
next prev parent 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 [PATCH 0/2] ci: avoid ugly "failure" annotation in the GitHub workflow Johannes Schindelin via GitGitGadget
2020-09-01 20:19 ` Johannes Schindelin via GitGitGadget [this message]
2020-09-02 0:33 ` [PATCH 1/2] ci: fix indentation of the `ci-config` job 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=b5363e282f69570e34ffb806f7a62e00e39b98bc.1598991568.git.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).