After detecting ANY matching change (added/changed/removed based on your filter settings), the NEXT check with identical content falsely triggers #3561
Conversation
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
…content falsely triggers
dgtlmoon
changed the title
…emoved lines), only limits the triggers of the change detection.
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.
After detecting ANY matching change (added/changed/removed based on your filter settings), the NEXT check with identical content falsely triggers
and now, the full snapshot is still saved (this does not strip added/changed/removed lines), only limits the triggers of the change detection.
You will need to use
{{diff_removed}}etc in your notificationAND does this add/remove/changed still properly restrict change alerts? what if i didnt set any other filter options, will it still alert me if i only 'remove' selected for example?