-
Notifications
You must be signed in to change notification settings - Fork 54
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
Change logic for finding plugin slug in CLI #367
Change logic for finding plugin slug in CLI #367
Conversation
5eca713
to
2eee538
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, @ernilambar, for the PR! I've provided some feedbacks. Aside from that, everything appears to be in good from my perspective.
PR updated as per the review comments. |
ad435fc
to
39844c9
Compare
39844c9
to
aa1df25
Compare
@mukeshpanchal27 After last commit, Behat test (PHP 8.0 WP Latest) is failing. Any idea? |
Does it pass locally for you? There might be some error/notice happening |
aa1df25
to
8d3ce4d
Compare
8d3ce4d
to
c89110c
Compare
I could not make it run Behat tests locally. Some database error occurs and tests fails even before starting. So I usually check those in GitHub Actions. |
The nikic/php-parser get updated from 4.18.0 to 5.0.0 in past few hours that may be issue as they update things related to PHP versions. cc. @swissspidy |
This project dos not use PHP-Parser, nor do any of the dependencies.
Have you tried running From what I can see in the logs, this failure started already at https://github.com/WordPress/plugin-check/actions/runs/7443210203 (though it worked fine on the PR branch itself) So it's not isolated to this PR. Unfortunately I'm unable to reproduce this locally right now, so let's deal with this in a separate PR to debug in more detail. No blocker for this PR. |
I've tested it locally, and it seems to be working fine for me as well. Not entirely sure why the issue persists. I've opened a dedicated issue to track and investigate that. Thank you! |
Fixes #364