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

Re: [PATCH 2/2] Improve check-whitespace output

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 16, 2022, 10:13 UTC
Message-ID
<xmqqh6xvmzb8.fsf@gitster.g>
In-Reply-To
<cdc2b1aae81f8c37b4e71cb3e0e382cf82de2272.1671179520.git.gitgitgadget@gmail.com>
"Chris. Webster via GitGitGadget" <gitgitgadget@gmail.com> writes:
> From: "Chris. Webster" <chris@webstech.net>
> Subject: Re: [PATCH 2/2] Improve check-whitespace output

The same comment about specificity of the improvements applies to this one, too. Also, I forgot to point out that our usual commit title takes the form of "<area>: <description>", e.g.

	Subject: [PATCH 2/2] ci: show $X in check.whitespace output

where "show $X" is meant to be a more concrete phrase than "improve" what the change is about and how it improves the output.

> +          echo "Run these commands to correct the problem:" >>$GITHUB_STEP_SUMMARY
> +          echo "1. \`git rebase --whitespace=fix ${goodparent}\`" >>$GITHUB_STEP_SUMMARY
> +          echo "1. \`git push --force\`" >>$GITHUB_STEP_SUMMARY

It's a bit curious to see two "1." and not "1." followed by "2." here. Is this meant to be processed by markdown or something so we do not have to do the numbering ourselves, or something?

Show 5 quoted lines
> +          echo " " >>$GITHUB_STEP_SUMMARY
> +          echo "Errors:" >>$GITHUB_STEP_SUMMARY
>            for i in "${problems[@]}"
>            do
>              echo "${i}" >>$GITHUB_STEP_SUMMARY
Thanks.
Previous: Chris. Webster via GitGitGadgetNext: Chris Webster
Message 3 of 18 in “Make check-whitespace failures more helpful”
  1. 0/2 Make check-whitespace failures more helpfulChris. Webster via GitGitGadget, Dec 16, 2022
  2. 2/2 Improve check-whitespace outputChris. Webster via GitGitGadget, Dec 16, 2022
  3. Junio C HamanoDec 16, 2022
  4. Chris WebsterDec 20, 2022
  5. 1/2 Make `check-whitespace` failures more helpfulChris. Webster via GitGitGadget, Dec 16, 2022
  6. Junio C HamanoDec 16, 2022
  7. Chris WebsterDec 20, 2022
  8. Junio C HamanoDec 20, 2022
  9. Chris WebsterDec 20, 2022
  10. 0/3 Make check-whitespace failures more helpfulChris. Webster via GitGitGadget, Dec 20, 2022
  11. 1/3 ci (check-whitespace): suggest fixes for errorsChris. Webster via GitGitGadget, Dec 20, 2022
  12. Đoàn Trần Công DanhDec 20, 2022
  13. Chris WebsterDec 20, 2022
  14. Đoàn Trần Công DanhDec 21, 2022
  15. Chris WebsterDec 21, 2022
  16. Đoàn Trần Công DanhDec 21, 2022
  17. 2/3 ci (check-whitespace): add links to job outputChris. Webster via GitGitGadget, Dec 20, 2022
  18. 3/3 ci (check-whitespace): move to actions/checkout@v3Chris. Webster via GitGitGadget, Dec 20, 2022

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.