Closed djboris88 closed 3 years ago
This has been fixed in https://github.com/rtCamp/action-phpcs-code-review/releases/tag/v2.0.4
Please use the latest tag @v2
when running the action. Please reopen this issue if the error continues.
One more question, since this action sets the CHANGES_REQUESTED status, once the phpcs errors are fixed, what is the flow supposed to be? The fix is not automatically recognized, even if the subsequential check passes, the change request still remains.
Once the errors are fixed, the reviews should become stale.
Should I just dismiss it?
Yes.
I am getting that same error, and have no idea how to fix it.
It happens all of a sudden, the same repo and PHPCS worked just fine for months.
Today I committed to same repo again and the bot can't complete the scan it fails with GitHub API communication error. Please contact a human.
It also breaks the actual scan by telling me there are files named wrongly, but it mentions files that do not even exist in the repo.
... What can be done?
Thanks!
I'm having the same issue as https://github.com/rtCamp/action-phpcs-code-review/issues/43, but I have created the token using a bot GitHub account.
Also, the log generated by this step is very, very long, more than 2700 lines when issues are found. There are many PHP Notices generated, for example:
One more question, since this action sets the
CHANGES_REQUESTED
status, once the phpcs errors are fixed, what is the flow supposed to be? The fix is not automatically recognized, even if the subsequential check passes, the change request still remains. Should I just dismiss it?