fix(.github/workflows): use literal pathspec when materializing PR module content - #1070
Merged
Conversation
DevelopmentCats
approved these changes
Aug 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Follow-up to #1069. The
/scorecardrun on #1068 detecteddroopy4096/mise-installcorrectly but failed at the materialize step:Wildcard pathspecs don't directory-prefix match the way literal paths do, so
registry/*/modulesmatched nothing. Fixed by overlaying the wholeregistry/tree instead, which is simpler and equally safe: it's all inert data read as text for the scoring prompt, and everything under.github/stays at the trusted base.Verified locally against
refs/pull/1068/merge: the checkout now materializesregistry/droopy4096/modules/mise-install.🤖 Generated with Coder Agents on behalf of @bpmct