From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/action-ci] 1e08fd: sync_repo: check workflow branch even when master ...
Date: Fri, 31 Jul 2026 10:30:58 -0700 [thread overview]
Message-ID: <bluez/action-ci/push/refs/heads/main/058d4c-1e08fd@github.com> (raw)
Branch: refs/heads/main
Home: https://github.com/bluez/action-ci
Commit: 1e08fd655d42fdf3e66a3909d086f165486cbb3f
https://github.com/bluez/action-ci/commit/1e08fd655d42fdf3e66a3909d086f165486cbb3f
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-07-31 (Fri, 31 Jul 2026)
Changed paths:
M sync_repo.sh
Log Message:
-----------
sync_repo: check workflow branch even when master is in sync
The script exited as soon as origin master matched upstream, so the
workflow branch was never checked and could stay stale indefinitely.
Drop the early exit and only gate the push to master on that
comparison, then always verify the workflow branch actually contains
every commit of master before deciding to rebase it.
The full (unshallow) fetch is moved up so it happens in both paths, and
the workflow branch checkout uses -B since the ref may already exist
locally after the fetch.
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/action-ci/settings/notifications
reply other threads:[~2026-07-31 17:30 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/058d4c-1e08fd@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