From 8be2f384c6528ae1588edefd633aa764b1998a24 Mon Sep 17 00:00:00 2001
From: Mayuko Moriyama <mayuko.moriyama@tarosky.co.jp>
Date: Mon, 3 Aug 2026 23:58:43 +0900
Subject: [PATCH] Add a workflow to update WordPress.org assets without a
 release

Assets currently only reach WordPress.org when a release is published,
so artwork committed to .wordpress-org/ stays invisible until the next
version ships.
---
 .github/workflows/asset-update.yml | 35 ++++++++++++++++++++++++++++++
 1 file changed, 35 insertions(+)
 create mode 100644 .github/workflows/asset-update.yml

diff --git a/.github/workflows/asset-update.yml b/.github/workflows/asset-update.yml
new file mode 100644
index 0000000..6415973
--- /dev/null
+++ b/.github/workflows/asset-update.yml
@@ -0,0 +1,35 @@
+name: Update WordPress.org assets
+
+on:
+  push:
+    branches:
+      - master
+    paths:
+      - '.wordpress-org/**'
+      - 'README.md'
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  assets:
+    name: Update assets on WordPress.org
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Setup PHP
+        uses: shivammathur/setup-php@v2
+        with:
+          php-version: 7.4
+
+      - name: Generate readme.txt
+        uses: tarosky/workflows/actions/wp-readme@main
+
+      - name: Update assets and readme on WordPress.org
+        uses: 10up/action-wordpress-plugin-asset-update@stable
+        env:
+          SVN_USERNAME: ${{ secrets.WP_ORG_USERNAME_TAROSKY }}
+          SVN_PASSWORD: ${{ secrets.WP_ORG_PASSWORD_TAROSKY }}