git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 0/2] ci: avoid ugly "failure" annotation in the GitHub workflow

From
Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>
Date
Sep 1, 2020, 20:19 UTC
Message-ID
<pull.719.git.1598991568.gitgitgadget@gmail.com>

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: Johannes Schindelin via GitGitGadget
Message 1 of 6 in “ci: avoid ugly "failure" annotation in the GitHub workflow”
  1. 0/2 ci: avoid ugly "failure" annotation in the GitHub workflowJohannes Schindelin via GitGitGadget, Sep 1, 2020
  2. 1/2 ci: fix indentation of the `ci-config` jobJohannes Schindelin via GitGitGadget, Sep 1, 2020
  3. Jeff KingSep 2, 2020
  4. 2/2 ci: avoid ugly "failure" in the `ci-config` jobJohannes Schindelin via GitGitGadget, Sep 1, 2020
  5. Jeff KingSep 2, 2020
  6. Junio C HamanoSep 2, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.