From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/action-ci] c1b86b: ci: add verify_fixes and verify_signedoff checks f...
Date: Thu, 21 May 2026 08:48:54 -0700 [thread overview]
Message-ID: <bluez/action-ci/push/refs/heads/main/80ebbf-c1b86b@github.com> (raw)
Branch: refs/heads/main
Home: https://github.com/bluez/action-ci
Commit: c1b86bca7cacc936bea82b3ca8b2ee4b4fcb6e74
https://github.com/bluez/action-ci/commit/c1b86bca7cacc936bea82b3ca8b2ee4b4fcb6e74
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-05-21 (Thu, 21 May 2026)
Changed paths:
M Dockerfile
M ci.py
M ci/__init__.py
A ci/verifyfixes.py
A ci/verifysignedoff.py
A scripts/verify_fixes.sh
A scripts/verify_signedoff.sh
Log Message:
-----------
ci: add verify_fixes and verify_signedoff checks for kernel patches
Add scripts from gregkh/gregkh-linux adapted for GitHub Actions:
- verify_fixes.sh: validates Fixes: tag format, SHA existence, subject
match, and ancestry (removed external Linus tree dependency)
- verify_signedoff.sh: validates author/committer Signed-off-by presence
Both run against origin/master..HEAD after checkpatch in the kernel CI
pipeline and report results as warnings to patchwork.
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/action-ci/settings/notifications
next reply other threads:[~2026-05-21 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 15:48 Luiz Augusto von Dentz [this message]
2026-06-05 10:10 ` [bluez/action-ci] c1b86b: ci: add verify_fixes and verify_signedoff checks f Bastien Nocera
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=bluez/action-ci/push/refs/heads/main/80ebbf-c1b86b@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@vger.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