MPTCP Linux Development
 help / color / mirror / Atom feed
From: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
To: mptcp@lists.linux.dev
Cc: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
Subject: [PATCH mptcp-next] gh: fix summary title's level
Date: Thu, 15 Feb 2024 18:50:44 +0100	[thread overview]
Message-ID: <20240215175043.3707650-2-matttbe@kernel.org> (raw)

Even if the doc suggests to use the 3rd level, it looks like other
Actions use the 2nd level.

Do the same on our side not to have our summary included under another
one.

Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
---

Notes:
    Sorry for the noise: I usually don't send patches for modifications
    touching the CI files -- mainly because it is quite specific, and our
    team is too small to have multiple people working on that, and reviewing
    these modifications too -- but here we wanted to validate Patchew after
    having applied a hot patch with Davide: the goal is not to re-apply
    patches when tags -- Reviewed-by, etc. -- are shared on the ML, not to
    waste CI resources.

 .github/workflows/checkpatch.yml | 2 +-
 .github/workflows/tests.yml      | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/checkpatch.yml b/.github/workflows/checkpatch.yml
index df31d122d674..f70de5d1bfda 100644
--- a/.github/workflows/checkpatch.yml
+++ b/.github/workflows/checkpatch.yml
@@ -45,7 +45,7 @@ jobs:
         if: always()
         run: |
           if [ -s "${{ env.DETAILS }}" ]; then
-            echo '### Results' >> $GITHUB_STEP_SUMMARY
+            echo '## Results' >> $GITHUB_STEP_SUMMARY
             cat "${{ env.DETAILS }}" >> $GITHUB_STEP_SUMMARY
           fi
 
diff --git a/.github/workflows/tests.yml b/.github/workflows/tests.yml
index e12bba92b4ee..4a406ec5f687 100644
--- a/.github/workflows/tests.yml
+++ b/.github/workflows/tests.yml
@@ -72,7 +72,7 @@ jobs:
         if: always()
         run: |
           if [ -s "conclusion.txt" ]; then
-            echo '### Conclusion' >> $GITHUB_STEP_SUMMARY
+            echo '## Conclusion' >> $GITHUB_STEP_SUMMARY
             cat "conclusion.txt" >> $GITHUB_STEP_SUMMARY
           fi
 

base-commit: 52e05de42e1094a943053af93ea08c51a44091f7
-- 
2.43.0


                 reply	other threads:[~2024-02-15 17:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240215175043.3707650-2-matttbe@kernel.org \
    --to=matttbe@kernel.org \
    --cc=mptcp@lists.linux.dev \
    /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