It should be possible to annotate files that are not in the commit

[mattnewport]

Annotations can be generated for errors but if the error is in a file that is not part of the commit then it will just link to a line in an unrelated file that is part of the commit. It should be possible to link to files that are not part of the commit.

A simple example of where this is needed: if I have a C# project with two code files and remove a method from one that is called from the other then I will get a compiler error in the unchanged file that is calling the now removed method. Currently the annotations will display the correct filename the compiler error refers to but will link to the wrong file in the commit rather than to the correct file elsewhere in the repo that wasn't touched in this commit.

As far as I can tell this isn't currently possible. If it is possible it should be documented how for problem matchers.

Describe the enhancement

Annotations should be able to link to a file and line / column number anywhere in the repo and not only in the commit. This should be possible from problem matchers (the context in which I originally ran into this issue).

[peternewman]

It does sometimes seem to happen @mattnewport , although I'm not really clear of the logic for when. Annotations are always generated but only show in some PRs, for example here:
https://github.com/peternewman/rdm-app/pull/14/files

See the "Unchanged files with check annotations" section, which is also marked as beta.

[jsg2021]

It would be nice to have the link go to the file (unchanged or not). Isn't there a tree-view for each commit?

[alanmehio]

@mattnewport . Any idea if there is a solution to this github beta annotation see this PR