-
-
Notifications
You must be signed in to change notification settings - Fork 334
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add cs2pr support #161
Comments
@staabm Also how does |
thx for your fast feedback.
not sure if this has a benefit. the script actual is a single file: do you see any advantages of having it as a phar?
phpunit is not supported, because it does not support the checkstyle format. I have already discussed it with sebastian, but he does not like the idea of having checkstyle-reports in phpunit: there is a small tool though, which brings the same functionality with phpunit
never heared of this feature.. this sounds interessting.. maybe phpunit-github-actions-printer is not required then. how does this problem-matcher work? what content is expected in phpunit.json ? how to produce this file? |
@staabm Creating annotations in GitHub Actions requires a Here is the json file for creating annotations for This comment explains each regex in the json file - #84 (comment) |
It would be a HUGE improvement; ❤️ |
thx for the additional info. wasnt aware that problem matches are a thing.
just added the cs2pr file to the 1.0 release. can you work with that or do you need more? https://github.com/staabm/annotate-pull-request-from-checkstyle/releases/tag/1.0 |
@staabm Thanks. will add support in next release. |
If possible, provide some example @shivammathur in the documentation; Thank you guys about this. |
Thank you |
works like a charm <2. thanks again |
I recently published a tiny little script which allows to add github pull request annotations based on checkstyle formatted error reports.
see e.g.
this is usefull in combination with phpstan, psalm, php-cs-fixer or any other tool which supports the checkstyle format.
my tool is only usefull in github actions context and I guess will mostly be used in the php world.
what do you think about bunling the script with this great setup-php github action?
that way people could use the script very easily.
what do you think?
https://github.com/staabm/annotate-pull-request-from-checkstyle
The text was updated successfully, but these errors were encountered: