From: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
To: "Kernel.org Tools" <tools@kernel.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
"Matthieu Baerts (NGI0)" <matttbe@kernel.org>
Subject: [PATCH b4 3/3] review: patchwork: use the target URL
Date: Tue, 28 Apr 2026 11:29:16 +0200 [thread overview]
Message-ID: <20260428-sashiko-patchset-api-v1-3-24d4ac34b4ae@kernel.org> (raw)
In-Reply-To: <20260428-sashiko-patchset-api-v1-0-24d4ac34b4ae@kernel.org>
The 'url' field from the 'checks' endpoint is pointing to the Patchwork
API, not very interesting to display, e.g.
https://patchwork.kernel.org/api/patches/14521024/checks/9433123/
Instead, use the 'target_url' which typically points to something useful
linked to the results: more details, logs, etc. e.g.
https://github.com/multipath-tcp/mptcp_net-next/actions/runs/24274365064
Assisted-by: Not-my-dog
Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
---
src/b4/review/checks.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/b4/review/checks.py b/src/b4/review/checks.py
index 942935e..96c769e 100644
--- a/src/b4/review/checks.py
+++ b/src/b4/review/checks.py
@@ -333,7 +333,7 @@ def _run_builtin_patchwork(
'status': status,
'state': state,
'description': check.get('description', ''),
- 'url': check.get('url', ''),
+ 'url': check.get('target_url', ''),
}
)
--
2.53.0
prev parent reply other threads:[~2026-04-28 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 9:29 [PATCH b4 0/3] review: avoid downloading logs and fix URLs Matthieu Baerts (NGI0)
2026-04-28 9:29 ` [PATCH b4 1/3] review: sashiko: switch to patchset endpoint Matthieu Baerts (NGI0)
2026-04-28 9:29 ` [PATCH b4 2/3] review: sashiko: fix URLs Matthieu Baerts (NGI0)
2026-04-28 9:29 ` Matthieu Baerts (NGI0) [this message]
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=20260428-sashiko-patchset-api-v1-3-24d4ac34b4ae@kernel.org \
--to=matttbe@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=tools@kernel.org \
/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