Repository navigation
Read a flag the page says implies check mode as check mode - #23
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
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.
The gate rerun at e62f2e5 left one false FAIL: pinact's sarif page runs the tool with a flag the page itself says implies --fix=false, and the tool exited 1 with a SARIF report of files that need pinning, which pinact's exit-code page documents. A sentence saying one flag implies a flag already in the check-mode set now makes that flag check mode for the document, with its value as written, and an explicit --fix beside it turns fixing back on. Plan A/B over the 42 pinned clones moves only that one line. DESIGN.md records the rule.