You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The annotation engine should first check the commit if the file was edited in the current commit. If not, then it should do the equivalent of git log --follow -n 1 <filepath> to find the most recent commit and generate the annotation and link on that commit.
Alternatively the frontend link engine could be smart enough that, if an annotation is defined on a commit but the file doesn't exist in the commit, then do the equivalent above to find the file in a previous commit that the annotation was referencing and present it. This would probably be a smarter approach to avoid annotations "leaking" into parent branches.
NOTE: if the feature request has been agreed upon then the assignee will create an ADR. See docs/adrs/README.md
The text was updated successfully, but these errors were encountered:
This issue does not seem to be a problem with the runner application, it concerns the GitHub actions platform more generally. Could you please post your feedback on the GitHub Community Support Forum which is actively monitored? Using the forum ensures that we route your problem to the correct team. 😃
Enhancement Description
Often an annotation may reference a file that isn't present in the latest file of a commit.
For example:
https://github.com/JustinGrote/Super-Duper-Linter/actions/runs/146628514
JustinGrote/Super-Duper-Linter@8925755#annotation_266417563
Recommended Resolution
The annotation engine should first check the commit if the file was edited in the current commit. If not, then it should do the equivalent of
git log --follow -n 1 <filepath>
to find the most recent commit and generate the annotation and link on that commit.Alternatively the frontend link engine could be smart enough that, if an annotation is defined on a commit but the file doesn't exist in the commit, then do the equivalent above to find the file in a previous commit that the annotation was referencing and present it. This would probably be a smarter approach to avoid annotations "leaking" into parent branches.
NOTE: if the feature request has been agreed upon then the assignee will create an ADR. See docs/adrs/README.md
The text was updated successfully, but these errors were encountered: