-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Select no tests if modified-only
returns nothing
#2761
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
fbfd0e0
to
3b3056f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix, looks good. Do you still plan to add a release not as suggested by the checklist?
modified-only
returns nothing
No idea. Any preference? On one side it changes behavior but on the other it changes it to the expected one. |
Yeah, in fact, it just fixes a bug, and probably not that interesting --> I suggest to skip the release note. |
Hm, |
I'll take a look in the afternoon. That test used to pass before the rebase. |
Previously it selected all tests. Now it respects that if nothing is modified then nothing is selected. Fix: #2449
3b3056f
to
48c8a85
Compare
Ah, right. I broke it in fbfd0e0. Fixed now. Tests are good. |
Failing tests are known culprits --> merging. |
Previously it selected all tests. Now it respects that if nothing is modified then nothing is selected. Fix: teemtee#2449
Previously it selected all tests. Now it respects that if nothing is modified then nothing is selected.
Fix: #2449
Is this worth of release note?
Pull Request Checklist