From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] b73ba1: github: Add YAML issue template and btsnoop-analyz...
Date: Thu, 16 Apr 2026 11:07:39 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/150806-ce07e9@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: b73ba12b0bd62211609e1f6c94af780950a628ee
https://github.com/bluez/bluez/commit/b73ba12b0bd62211609e1f6c94af780950a628ee
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-04-16 (Thu, 16 Apr 2026)
Changed paths:
R .github/ISSUE_TEMPLATE/issue.md
A .github/ISSUE_TEMPLATE/issue.yml
A .github/workflows/btsnoop-analyzer.yml
Log Message:
-----------
github: Add YAML issue template and btsnoop-analyzer workflow
Replace the markdown issue template with a structured YAML form that
includes fields for description, reproduction steps, btmon trace upload,
analysis focus area selection, and privacy consent checkboxes.
Add a btsnoop-analyzer workflow that automatically analyzes btsnoop
traces attached to new issues using Vudentz/btsnoop-analyzer action,
posting results as issue comments.
Commit: ec6940c1a28413d5b7f52be27216cd1997653ced
https://github.com/bluez/bluez/commit/ec6940c1a28413d5b7f52be27216cd1997653ced
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-04-16 (Thu, 16 Apr 2026)
Changed paths:
M .github/workflows/btsnoop-analyzer.yml
Log Message:
-----------
github: Make result posting robust against action failures
Use always() conditions with file-existence checks so steps 1-4
results are posted even if the btsnoop-analyzer action fails
partway through. The error comment now only fires on actual action
failure (e.g. btmon build error), not LLM errors which are handled
gracefully by the analyzer.
Commit: ce07e906e49998c32d5a3d3245bc8b1245e3b368
https://github.com/bluez/bluez/commit/ce07e906e49998c32d5a3d3245bc8b1245e3b368
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-04-16 (Thu, 16 Apr 2026)
Changed paths:
A .github/workflows/btsnoop-analyze.yml
Log Message:
-----------
github: Add btsnoop-analyzer slash command workflow
Add caller workflow for the btsnoop-analyzer reusable workflow,
enabling trace analysis from any issue comment.
Compare: https://github.com/bluez/bluez/compare/15080642a414...ce07e906e499
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-04-16 18:07 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/150806-ce07e9@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