Can I build from a specific tag on the same master branch?
#186
-
|
Hello Developer! Thank you for maintaining this great project! I have a question: Can I build from a specific tag on the same on: [push, pull_request, workflow_dispatch]
jobs:
build:
uses: zmkfirmware/zmk/.github/workflows/build-user-config.yml@mainshould be working and build the |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
Hi there. The keymap editor itself doesn't actually handle building the firmware, it just integrates with GitHub APIs to link to the most recently completed build. If you're talking about building from a specific ZMK version, look at your repository's You can specify the tag name after |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for explaining this to me! And I want to keep using the default latest ZMK version. Actually I'm talking about my tags in my own Could you kindly also provide me some advice on this? I know Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Ah, I understand now. This isn't anything I'd want to mess with in the app, I think it'd a bit too complex to be worth it. If you already have the tag created you can go to the Actions tab in your GitHub repo, select Build, and then Run Workflow on the right. In the popup you can select a tag/branch to build from. Edit: to automatically build both the current version and the tagged version would take some creativity with the |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much! I don't know that I can checkout to that tag on github website and manually trigger the action for once. lol |
Beta Was this translation helpful? Give feedback.
Ah, I understand now.
This isn't anything I'd want to mess with in the app, I think it'd a bit too complex to be worth it. If you already have the tag created you can go to the Actions tab in your GitHub repo, select Build, and then Run Workflow on the right. In the popup you can select a tag/branch to build from.
Edit: to automatically build both the current version and the tagged version would take some creativity with the
build-user-configworkflow. If it's important you could hack around it by copying the "known good" version of the keymap into the repo with a different name (e.g.corne-original.keymap) and then duplicating the relevant corne files to build another corne keyboard... m…