fix: make trigger_phrase matching case-insensitive #915
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
i(case-insensitive) flag to all fourRegExpconstructions incheckContainsTrigger@claudeto@ClaudeProblem
The
trigger_phraseregex was constructed without theiflag, making matching case-sensitive. GitHub's workflow-levelcontains()guard is case-insensitive, so the workflow would run but the action's internal check would silently reject the trigger — a confusing UX gap.Changes
src/github/validation/trigger.ts: Added"i"flag to all 4new RegExp()callstest/trigger-validation.test.ts: Addedcase-insensitive trigger matchingdescribe block with tests for@Claude,@CLAUDE, and@cLaUdEvariantsTest plan
bun test test/trigger-validation.test.ts)bun run typecheck)bun run format:check)Fixes #910