From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/action-ci] fa1938: sync_patchwork: don't recreate a PR that was alrea...
Date: Thu, 10 Sep 2026 12:45:14 -0700 [thread overview]
Message-ID: <bluez/action-ci/push/refs/heads/main/08efb9-fa1938@github.com> (raw)
Branch: refs/heads/main
Home: https://github.com/bluez/action-ci
Commit: fa19384d4c70f1cfd7e432aab9a2f731dadb7091
https://github.com/bluez/action-ci/commit/fa19384d4c70f1cfd7e432aab9a2f731dadb7091
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-09-10 (Thu, 10 Sep 2026)
Changed paths:
M libs/githubtool.py
M sync_patchwork.py
Log Message:
-----------
sync_patchwork: don't recreate a PR that was already closed
The series to process are picked from the patchwork state, and the only
thing that kept a series from being processed again was an open pull
request with its id in the title. Closing a stale pull request removed
that marker, so the next run recreated the pull request, ran the CI again
and sent a second result summary to the same thread:
#652 [PW_SID:1151528] ... created 2026-08-25, closed 2026-09-10 18:05
#746 [PW_SID:1151528] ... created 2026-09-10 18:11
Look the closed pull requests up as well so a series is handled only once.
A resent series always gets a new series id from patchwork and is still
picked up.
The series id is now matched exactly too. The old substring match made,
for example, PW_SID:115152 match a pull request for PW_SID:1151528 and the
series was silently never tested.
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/action-ci/settings/notifications
reply other threads:[~2026-09-10 19:45 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/action-ci/push/refs/heads/main/08efb9-fa1938@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