Closed mitchspano closed 1 year ago
This should be resolved with the latest release of 0.1.8 with the improved scope filtering.
The action's output will now also print out the changed lines for each file to help identify issues like this in the future.
When renaming a file, it is possible for the action to attempt to comment on lines which it rightly identifies as part of the git difference, but are outside of the range of allowed lines for the GitHub REST API to generate a comment for.
In this example, the
MyClass.cls
file was renamed toSomeClass.cls
:The scanner identified a finding which was applicable to the whole class, but the 12th line was not included in the "commentable" lines for GitHub REST API.