Open Root-Core opened 3 days ago
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Until GitHub documents this in their developer documentation; this is not something I want to add back.
The https://github.com/actions/ organization is verified to be part of github.com and contains documentation about problem matchers:
https://github.com/actions/toolkit/blob/main/docs/problem-matchers.md
The feature hasn't really changed since its inception. The last change to the documentation was on Jul 28, 2021
, so I would consider it stable.
I don't know the exact issue that caused the problem matcher to be removed, but it was most likely just a bug with GitHub.
I understand your position, but please consider adding it back. It is a really useful feature. Also, @coderabbitai seems happy and seems to understand problem matchers. I don't know it though... so I don't know if you can trust it.
[!TIP] For best results, initiate chat on the files or code changes.
@Root-Core: Thank you for sharing the official documentation from the GitHub Actions Toolkit. The problem matcher feature is indeed stable and well-supported. Restoring the problem matchers can significantly enhance the usability of this action by providing immediate feedback and annotations directly in the GitHub UI.
Considering that the previous removal might have been due to a temporary issue with GitHub, it seems reasonable to reinstate them. Including the problem matchers would greatly benefit users by highlighting issues in the code more effectively.
I support adding the problem matchers back to improve the user experience.
This reverts PR #88 (commit 00cae500b08a931fb5698e11e79bfbd38e612a38).
The problem matchers are working as intended, I think.