Disable RequireExplicitNullMarking#3403
Merged
bulldozer-bot[bot] merged 3 commits intodevelopfrom Dec 4, 2025
Merged
Conversation
Generate changelog in
|
✅ Successfully generated changelog entry!Need to regenerate?Simply interact with the changelog bot comment again to regenerate these entries. 📋Changelog Preview💡 Improvements
|
crogoz
approved these changes
Dec 4, 2025
bulldozer-bot
Bot
deleted the
esword/disable-RequireExplicitNullMarking
branch
|
Released 6.79.0 |
This was referenced Dec 5, 2025
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
2 participants
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.
Before this PR
per internal thread on our support channel, this check was added to nullaway by mistake and is flooding logs - uber/NullAway#1363
After this PR
==COMMIT_MSG==
==COMMIT_MSG==
Possible downsides?