Changing behaviour of PytestReturnNotNoneWarning to return a warning#11211
Merged
nicoddemus merged 3 commits intopytest-dev:mainfrom Sep 7, 2023
Merged
Changing behaviour of PytestReturnNotNoneWarning to return a warning#11211nicoddemus merged 3 commits intopytest-dev:mainfrom
nicoddemus merged 3 commits intopytest-dev:mainfrom
Conversation
nicoddemus
approved these changes
Sep 7, 2023
Member
nicoddemus
left a comment
nicoddemus
left a comment
There was a problem hiding this comment.
Thanks @fraserstark for the contribution!
Sorry this got lost in the noise and took so long to review.
nicoddemus
force-pushed
the
fix-not-none-warning
branch
from
82afa60 to
1793204
Compare
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.
head-fork: fraserstark/pytest
compare: fix-not-none-warning
base-fork: pytest-dev/pytest
base: main
Fixes #10465
This is my first contribution, I'm not sure if I've used the correct name for the changelog entry so perhaps someone can let me know and I'll adjust if necessary.