@lildude thanks for the feedback! I've updated with some heuristics.

.action does not meet out usage requirements

Curious what the requirements are – the one I saw in the template was "used in hundreds of repositories"?

It's true that both .srv and .action are less commonly used than .msg, but they are equally first-class citizens in ROS (and the syntax is basically identical so the same heuristics mostly apply). Is there any way to do something like "if the repository also has ROS .msg files, then assume the .action files in the same repo are ROS too"?

Both .srv and .action files also have a requirement that they must have at least one "---" line, which I think gives us a pretty good chance of matching correctly with heuristics. Because the syntax is minimal I was also able to add a negative_pattern which should filter out most non-ROS files.

I'm also not quite sure what is wrong with the current test failures...do I need to add more samples?

Curious what the requirements are – the one I saw in the template was "used in hundreds of repositories"?

Note the issue referenced.

I'm also not quite sure what is wrong with the current test failures...do I need to add more samples?

The failures indicate your heuristic regular expressions don't match the content of your samples. This will be because they're not valid (unescaped /). They're also vulnerable to ReDos attack. Please fix these and make your regexes PCRE2 compliant (I plan to make this a requirement soon).

Thanks for the tips. I believe I've fixed the redos issue, although couldn't quite figure out how to get codeql up and running in my local working copy to verify, but I did check against https://makenowjust-labs.github.io/recheck/playground/. As for PCRE2 compatibility, I believe they already were and still are compatible according to https://regex101.com, but let me know if you're seeing otherwise.

Here are some search queries using the actual heuristic regexes I'm adding: msg, srv, action