From a8660ed2d4fe48139fd7bf35a6c6324b828c65fa Mon Sep 17 00:00:00 2001
From: zackees <zachvorhies@protonmail.com>
Date: Sat, 20 Jun 2026 14:57:53 -0700
Subject: [PATCH] chore: rename nightly-usb-ids workflow to update-data

The workflow now refreshes multiple datasets (USB-VID + PlatformIO
boards + slim vendor_boards view), so the file name + display name no
longer reflect its scope. Rename to "Update data" and update the few
docs / source comments that referenced the old name.

Side-effect: GitHub's workflow run history is keyed by file path, so
existing run history under "Nightly USB IDs refresh" becomes stranded
in the Actions UI. New runs appear under "Update data". Acceptable cost
for a clearer name.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
---
 .../{nightly-usb-ids.yml => update-data.yml}         | 12 ++++++------
 crates/fbuild-core/examples/dump_usb_ids.rs          |  2 +-
 docs/online-data.md                                  |  4 ++--
 3 files changed, 9 insertions(+), 9 deletions(-)
 rename .github/workflows/{nightly-usb-ids.yml => update-data.yml} (98%)

diff --git a/.github/workflows/nightly-usb-ids.yml b/.github/workflows/update-data.yml
similarity index 98%
rename from .github/workflows/nightly-usb-ids.yml
rename to .github/workflows/update-data.yml
index 43239bfb..c363cfe8 100644
--- a/.github/workflows/nightly-usb-ids.yml
+++ b/.github/workflows/update-data.yml
@@ -39,9 +39,9 @@
 #     branch keeps its last good snapshot.
 #   - History is pruned to the most recent 200 commits per the design.
 #
-# Manual trigger: Actions tab → "Nightly online-data refresh" → Run.
+# Manual trigger: Actions tab → "Update data" → Run workflow.
 
-name: Nightly online-data refresh
+name: Update data
 
 on:
   schedule:
@@ -54,7 +54,7 @@ permissions:
   contents: write
 
 concurrency:
-  group: nightly-online-data
+  group: update-data
   cancel-in-progress: false
 
 env:
@@ -64,8 +64,8 @@ env:
   HISTORY_LIMIT: 200
 
 jobs:
-  refresh:
-    name: Refresh online-data datasets
+  update:
+    name: Update online-data datasets
     runs-on: ubuntu-latest
     steps:
       - name: Checkout main (default branch)
@@ -293,7 +293,7 @@ jobs:
         if: always()
         run: |
           {
-            echo "## Nightly online-data refresh"
+            echo "## Update online-data"
             echo ""
             echo "| source / step | outcome |"
             echo "|---|---|"
diff --git a/crates/fbuild-core/examples/dump_usb_ids.rs b/crates/fbuild-core/examples/dump_usb_ids.rs
index 206955e3..76c54596 100644
--- a/crates/fbuild-core/examples/dump_usb_ids.rs
+++ b/crates/fbuild-core/examples/dump_usb_ids.rs
@@ -1,7 +1,7 @@
 //! Dump the bundled `usb-ids` database as a JSON object to stdout.
 //!
 //! Used by the `online-data` branch's nightly workflow (see
-//! `.github/workflows/nightly-usb-ids.yml`) as one of the input sources
+//! `.github/workflows/update-data.yml`) as one of the input sources
 //! for the merged `usb-vid.json`. Running this example via
 //! `soldr cargo run --release --example dump_usb_ids -p fbuild-core`
 //! captures the exact data the bundled `usb-ids` crate version we depend
diff --git a/docs/online-data.md b/docs/online-data.md
index 52406c9d..e7105f38 100644
--- a/docs/online-data.md
+++ b/docs/online-data.md
@@ -61,7 +61,7 @@ the merger script and commit results.
 
 ## How a refresh happens
 
-`.github/workflows/nightly-usb-ids.yml` is the only workflow that touches
+`.github/workflows/update-data.yml` is the only workflow that touches
 `online-data`. It lives on `main` because GitHub Actions requires `schedule`
 and `workflow_dispatch` triggers to be defined on the default branch.
 
@@ -92,7 +92,7 @@ Per run:
 9. `git push --force-with-lease origin online-data` (the force is needed
    only when history was pruned).
 
-Manual trigger: Actions → "Nightly USB IDs refresh" → Run workflow.
+Manual trigger: Actions → "Update data" → Run workflow.
 
 ## Fault tolerance contract