Fix correctness build #65789
Merged
Fix correctness build #65789
Conversation
This file contains 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
jasonmalinowski
approved these changes
Dec 5, 2022
ghost
added this to the 
|
Force merging since the validation leg that was broken is now fixed, and we don't imagine a way editing a markdown file can break anything else. |
|
Ah, my bad. Sorry about the break. |
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.
#65729 (added a new analyzer) and #62242 (added new rule violated by analyzer) merged independently without CI re-triggering.
The temporary fix here is to add the new rule to the allow list until documentation can be added (cc @CyrusNajmabadi for tracking that).