From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 9dffe6: doc: Add AI coding assistants guidelines
Date: Tue, 21 Apr 2026 13:34:09 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/0fdf34-2c3961@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 9dffe61bd8b270681a1aa6d30f8819718c2d5a61
https://github.com/bluez/bluez/commit/9dffe61bd8b270681a1aa6d30f8819718c2d5a61
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-04-21 (Tue, 21 Apr 2026)
Changed paths:
M README
A doc/coding-assistants.rst
Log Message:
-----------
doc: Add AI coding assistants guidelines
Add doc/coding-assistants.rst with guidance for AI tools contributing to
BlueZ, covering licensing compatibility, human responsibility, and the
Assisted-by attribution format. Reference the new document from the README.
Based on similar documentation from the Linux kernel:
78d979db6cef ("docs: add AI Coding Assistants documentation")
Commit: 2c3961e3b0fab02afa3b8388e35f190c96f94fdb
https://github.com/bluez/bluez/commit/2c3961e3b0fab02afa3b8388e35f190c96f94fdb
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-04-21 (Tue, 21 Apr 2026)
Changed paths:
M .github/workflows/btsnoop-analyze.yml
Log Message:
-----------
Add permissions for btsnoop-analyzer workflow
Grant issues:write, contents:read, and models:read so the reusable
workflow can post comments and access the GitHub Models API.
Compare: https://github.com/bluez/bluez/compare/0fdf34b17d41...2c3961e3b0fa
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-04-21 20:34 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=bluez/bluez/push/refs/heads/master/0fdf34-2c3961@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.