Herald "Changed file content" triggers on old lines which are being removed

Hi. Is there any way to constrain the herald rule so only the new version of the file gets checked?
We often use it to flag some functions which are deprecated, to dissuade any new use of it,
but it currently also triggers on commits where it’s being removed, thus only in the old/left version.
i.e. this is correct behavior and should not be alarmed by the triggered herald.

If not currently possible, could you please file as a feature request?

Thanks in advance,
-neil

Use the Herald condition “Added file content” (which selects modified content in the new file only) instead of “Changed file content” (which selects modified content in the old or new files).