Ensure non-ASCII API assets trigger deployment builds - #345
Merged
Conversation
Constraint: Driver guide assets use Korean filenames and must trigger delivery-api rebuilds.\nRejected: Rename the published guide to ASCII | the protected API contract and document identity should remain stable.\nConfidence: high\nScope-risk: narrow\nDirective: Keep core.quotePath disabled wherever Git path output feeds scope matching.\nTested: deploy contract test, classifier test with Korean fixture, env authority test, git diff check\nNot-tested: GitHub-hosted workflow execution before push
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
1 participant
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.
Summary
Why
The protected Driver guide uses a Korean filename. Git default quoted path output prevented the apps/delivery-api/ scope matcher from seeing it, so a successful deploy reused the previous API image.
Verification