Skip to content

ci: expose rmk_version input and scope the push trigger - #2

Open
HaoboGu wants to merge 1 commit into
masterfrom
feat/expose-rmk-version
Open

ci: expose rmk_version input and scope the push trigger#2
HaoboGu wants to merge 1 commit into
masterfrom
feat/expose-rmk-version

Conversation

@HaoboGu

@HaoboGu HaoboGu commented Jul 13, 2026

Copy link
Copy Markdown
Collaborator

What

Makes the RMK version selectable in cloud builds, and stops rebuilding firmware on unrelated edits.

Changes

  • rmk_version input — the reusable workflow (haobogu/rmk/.github/workflows/user_build.yml) already accepts rmk_version, but this template never surfaced it, so every fork was pinned to main. workflow_dispatch now exposes it (default main) and threads it through; pushes stay on main.
  • Scoped push trigger — was paths: ["**"] (rebuilt on any file, including README edits). Now only keyboard.toml / vial.json.
  • README — the repo had none; adds a short guide to cloud builds and the version knob.

Existing forks are unaffected: the input is optional and defaults to main.

Surface the reusable workflow's rmk_version input via workflow_dispatch so forks can build against a released RMK version (default: main); previously every fork was stuck on main because this file never passed it through.

Scope the push trigger to keyboard.toml/vial.json so README/other edits don't trigger a firmware rebuild. Add a README covering cloud builds and the version knob.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant