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,