the intention being to catch commits which declare themselves as
cherry-picks, but either:
- don't refer to a commit in the master or staging branches
- are significantly altered from their original commit
determining the latter is not an exact science, but the heuristic of
looking for differences in only the added or removed lines seems to
work quite well. still, this should be considered an assistant
for reviewers rather than a hard failure. unfortunately github
workflows don't have a way of raising a gentle warning instead of a
failure.
the formatting of the output also leaves something to be desired due
to the limitations of github actions' "group" commands.
