From 8e619b76478273bbdb0aae7dc9ae1160a3ff73e9 Mon Sep 17 00:00:00 2001
From: Claude <noreply@anthropic.com>
Date: Tue, 31 Mar 2026 21:07:16 +0000
Subject: [PATCH] Point CI to Keebart's Vial-QMK fork for keyboard definition

The QMK userspace overlay only supports keymaps and user code, not
adding entirely new keyboard definitions. Since keebart/corne_choc_pro
only exists in Keebart's fork, the CI must clone that fork instead of
official qmk/qmk_firmware.

https://claude.ai/code/session_01G7xpKdeQFVBvr4iCzxrcTU
---
 .github/workflows/build_binaries.yaml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/build_binaries.yaml b/.github/workflows/build_binaries.yaml
index f7908fad..f53c3c81 100755
--- a/.github/workflows/build_binaries.yaml
+++ b/.github/workflows/build_binaries.yaml
@@ -10,8 +10,8 @@ jobs:
     name: 'QMK Userspace Build'
     uses: qmk/.github/.github/workflows/qmk_userspace_build.yml@main
     with:
-      qmk_repo: qmk/qmk_firmware
-      qmk_ref: master
+      qmk_repo: Keebart/vial-qmk-corne-choc-pro
+      qmk_ref: vial
 
   publish:
     name: 'QMK Userspace Publish'