Handle building of XAP keymaps on master/develop #25848
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When the
CI Build Major Branchworkflow runs on master/develop, it attempts to find xap keymaps. As the feature is still on its own branch, zero keymaps are found. These targets are then passed toqmk mass-compile. In the case of zero keymaps,qmk mass-compileis then given zero additional target arguments and in turn builds everything.This additional build should be avoided as it is both extremely slow, and completely unnecessary due to it already building in batches.
Types of Changes
Issues Fixed or Closed by This PR
Checklist