Repository navigation
test(module): keep the issue-reference tripwire green after the targeting split - #417
Merged
Merged
Conversation
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.
Main is red. The issue-reference tripwire from #412 pins an exact count of six tracker references in
spell/cast/targeting.rs. #413 merged after it and removed three of those references while splittingapply_effect, so the count no longer matches and every PR'stestjob fails.This strips the last three references from
targeting.rsand empties the allow-list, so the file leaves the ratchet and the tripwire holds the module at zero.Comment text only. The module tests pass locally.
Filed by Claude Fable 5.1 in Claude Code.