Since GitHub Actions is deprecating 'node12' actions, this now pops up warning annotations when it runs in a workflow.

See: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12

Since GitHub Actions is deprecating 'node16' actions, this now pops up warning annotations when it runs in a workflow.

See: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/

Hello!

I use meson + ninja for building my projects and that has ../ at the start of the file name, which isn't stripped so it doesn't pick up on the files.

Right now I've just bodged that into the regex here: https://github.com/Joshua-Ashton/gcc-problem-matcher but it might be something to look into to solve properly if Github allows it.

Thanks!

/^(?:(?:[^\s:]*): In .*\r?\n)?([^\s:]+):(\d+):(\d*):?\s+(?:fatal\s+)?(warning|error):\s+(.*)\r?\n(?:(?:\s+|In file included).*\r?\n)*(?:[^\s:]+:\d+:\d*:?\s+note:\s+.*\r?\n(?:(?:\s+|In file included).*\r?\n)*)*/

The full message (not just a regular expression locating the warning / error itself!) has a couple more lines of code.

Check this for example against:

/build/bzip2/compress.cpp: In function ‘void my_lib::bzip2::sendValues()’:
/build/bzip2/compress.cpp:365:30: warning: ISO C++1z does not allow ‘register’ storage class specifier [-Wregister]
             register int32_t a, b, c;
                              ^~~~~~
/build/bzip2/compress.cpp:365:30: note: ... don't do it.
In file included from /builds/a.h:10:0,
                 from /builds/b.h:11,
                 from /builds/c.h:27:

That's all just one single error message - and unless you plan on heading back to the full log just to understand the context, there's simply not enough captured by this problem matcher.

There is additional context before, and after the context captured in the current state.

Hi all

This github action is really interesting and I tried to use it. I managed to have it highlight the warnings in the build log but it does not create comments on the files. The screenshot in the README shows an example of such a comment I would like to have.

Is this action supposed to create these comments or do I have to combine it with another action to achieve that?

best regards

Since Github only shows 10 warnings in a run, it'd be nice if they were all from the actual project and not from a dependency, being able to ignore third_party, external, subprojects folders would be nice