Joakim Sørensen

@philhawthorne ping me if you get this working, then I can update the custom_component accordingly :)

While this is cool, I do not think this should be added here. This would be better as a standalone action.

In what case do you need your linters to run on custom runners? The code is already hosted on github, and you would never pass along any secrets to those...

I see, you should be able to split it up and run linters on default runners (which should go fast if you do not have millions of script files). Anyway,...

 This is from the problem-matcher, without it it would just be a regular output like the one above and below it. Why you don't see it on the "Summary"...

Yeah, before they did not, so I wrongly assumed they did not do it now, it seems they do. As for why/when/how it stopped I currently have no idea..

Actually, that highlighted warning is because of the problem-matcher. broken matcher on purpose on that run and it's no longer highlighted

Most likely not here, but I'm not sure, I have tried an older version that I know worked, and even those only show highlighting in the logs and nothing on...

There is a problem with the filename matching at least, but the same name that is extracted by the regex works when manually echoing a `::warning::` in the action, so...

For authentication have a look here