When CodeQL reports an issue parsing a file, the GitHub UI generates a file path that is absolute to the runner used to run CodeQL, rather than linking to the actual file in the repository.
That link to "View File" in that UI is something like the following:
https://github.com/Organization/Repository/blob/Repository//home/runner/work/Repository/Repository/path/to/file.rb#L300
Rather than the correct link which should be something like:
https://github.com/Organization/Repository/blob/develop/path/to/file.rb#L300
Impact
I wasted ~1hr of my time being stupid trying to figure out if that file was somehow getting generated as a simlinked file in our build or something. Finally realized that GitHub was just generating the link incorrectly.
When CodeQL reports an issue parsing a file, the GitHub UI generates a file path that is absolute to the runner used to run CodeQL, rather than linking to the actual file in the repository.
That link to "View File" in that UI is something like the following:
Rather than the correct link which should be something like:
Impact
I wasted ~1hr of my time being stupid trying to figure out if that file was somehow getting generated as a simlinked file in our build or something. Finally realized that GitHub was just generating the link incorrectly.