public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ v2] workflows: Add sync action
Date: Tue, 22 Apr 2025 17:49:35 -0400	[thread overview]
Message-ID: <20250422214935.993192-1-luiz.dentz@gmail.com> (raw)

From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>

This adds sync action which was part of https://github.com/bluez/actions/
but it gets disabled every 60 days due to inactivity, in addition to
syncing with upstream repositories it also syncs with patchwork which
created the PR and then triggers ci action to do the testing.
---
 .github/workflows/sync.yml | 45 ++++++++++++++++++++++++++++++++++++++
 1 file changed, 45 insertions(+)
 create mode 100644 .github/workflows/sync.yml

diff --git a/.github/workflows/sync.yml b/.github/workflows/sync.yml
new file mode 100644
index 000000000000..cd85bdd478c3
--- /dev/null
+++ b/.github/workflows/sync.yml
@@ -0,0 +1,45 @@
+name: Sync Repositories and Patchwork
+on:
+  schedule:
+    - cron: "*/5 * * * *"
+
+jobs:
+  bluez:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v2
+    - uses: bluez/action-sync-repo@master
+      with:
+        src_repo: 'https://git.kernel.org/pub/scm/bluetooth/bluez.git'
+        src_branch: 'master'
+        dest_repo: 'bluez/bluez'
+        dest_branch: 'master'
+        secret_token: ${{ secrets.ACTION_TOKEN }}
+
+  bluetooth-next:
+    needs: bluez
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v2
+    - uses: bluez/action-sync-repo@master
+      with:
+        src_repo: 'https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git'
+        dest_repo: 'bluez/bluetooth-next'
+        for_upstream_branch: 'for-upstream'
+        secret_token: ${{ secrets.ACTION_TOKEN }}
+
+  patchwork:
+    needs: bluez
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v3
+
+    - name: Sync Patchwork
+      uses: tedd-an/bzcafe@main
+      with:
+        task: patchwork
+        space: user
+        github_token: ${{ secrets.ACTION_TOKEN }}
+        email_token: ${{ secrets.EMAIL_TOKEN }}
+        patchwork_token: ${{ secrets.PATCHWORK_TOKEN }}
+        patchwork_user: ${{ secrets.PATCHWORK_USER }}
-- 
2.49.0


             reply	other threads:[~2025-04-22 21:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22 21:49 Luiz Augusto von Dentz [this message]
2025-04-22 22:00 ` [PATCH BlueZ v2] workflows: Add sync action patchwork-bot+bluetooth
2025-04-24 15:56 ` [BlueZ,v2] " bluez.test.bot

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=20250422214935.993192-1-luiz.dentz@gmail.com \
    --to=luiz.dentz@gmail.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