You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's detected that defined threshold for min-coverage-changed-files property does not work properly in connection with setting 'fail-emoji'. Emoji for changed files always appear with positive sign even if threshold is not achieved.
But on PR comment I get emoji from setting 'pass-emoji' for changed file with coverage of 50.19% that's under thresholded 90%. Current picture from PR is depicted on the screenshot below:
Here emoji from setting 'fail-emoji' should have been set. But actually, pass-emoji is assigned that's wrong.
I verified, that on version 1.4 (later versions from 1.5 started working incorrectly for this function) it worked correctly. Let me put screenshot here (Just one thing, emoji settings did not exist on that version and appeared only from v1.5.):
Hint: may be this issue relates to already registered one #71
The text was updated successfully, but these errors were encountered:
It's detected that defined threshold for min-coverage-changed-files property does not work properly in connection with setting 'fail-emoji'. Emoji for changed files always appear with positive sign even if threshold is not achieved.
Let me put my example of the step configuration:
But on PR comment I get emoji from setting 'pass-emoji' for changed file with coverage of 50.19% that's under thresholded 90%. Current picture from PR is depicted on the screenshot below:
Here emoji from setting 'fail-emoji' should have been set. But actually, pass-emoji is assigned that's wrong.
I verified, that on version 1.4 (later versions from 1.5 started working incorrectly for this function) it worked correctly. Let me put screenshot here (Just one thing, emoji settings did not exist on that version and appeared only from v1.5.):
Hint: may be this issue relates to already registered one #71
The text was updated successfully, but these errors were encountered: