Also someone with the right access should fix this too (I can't see the instructions, unsurprisingly):
https://github.com/github/docs/blob/356dea8ed4a7e2720df173d7983b02313a9a4a26/content/code-security/code-scanning/troubleshooting-code-scanning/no-source-code-seen-during-build.md?plain=1#L14

Thank you for your contribution @peternewman! The repository uses TypeScript transpiled into Javascript: could you update the TypeScript file at src/error-matcher.ts and then running npm run build to auto-generate the transpiled JS file and mapping?

We'll look into updating the link in the official documentation as well — thanks again 💖

Hello! I've just been reminded that we are using a new shortlink — https://gh.io/troubleshooting-code-scanning/no-source-code-seen-during-build (the one referenced in the documentation) — which will allow us to avoid this problem in the future, as the link will handle the case where the docs URL changes in the future. Do you mind updating to this link as well? Thanks!

Everything looks good, you'll just need to run the build command again to regenerate the transpiled files to pass the failing PR check!

npm run build run on the root directory should give you some file changes ✨

Do you want a changelog entry for this?

* [ ]  Confirm the [changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) has been updated if necessary.

Thank you for your contribution @peternewman! The repository uses TypeScript transpiled into Javascript

Oops, I think I'd found that first during the code search, then edited the wrong file!

We'll look into updating the link in the official documentation as well — thanks again 💖

Excellent thanks.

Hello! I've just been reminded that we are using a new shortlink — https://gh.io/troubleshooting-code-scanning/no-source-code-seen-during-build (the one referenced in the documentation) — which will allow us to avoid this problem in the future, as the link will handle the case where the docs URL changes in the future. Do you mind updating to this link as well? Thanks!

Even better!

Everything looks good, you'll just need to run the build command again to regenerate the transpiled files to pass the failing PR check!

Yeah I was just waiting until I was in front of a proper machine not just doing it in a web browser!

The failing checks are unrelated to your PR. We'll work on resolving them, please hold tight 😄

It looks like it's all green now @angelapwen

Perhaps you should have enabled automerge! 😄

Ha, I was thinking that perhaps you'd want the pleasure of clicking the merge button 😆 I'll merge now! Thank you again 💖

Ha, I was thinking that perhaps you'd want the pleasure of clicking the merge button laughing I'll merge now! Thank you again sparkling_heart

I don't think I remember seeing it, and I don't think I'd expect to unless you've given me more rights to the repo than a normal user.