-
Notifications
You must be signed in to change notification settings - Fork 39
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
Allow static checks to be run against an arbitrary path #490
Allow static checks to be run against an arbitrary path #490
Conversation
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
I'm out of office until Monday but happy to review then. At first glance I'd say the Also, this would be an excellent candidate to write Behat tests for. Happy to help with both once I'm back. |
I tested PR and it is not working for plugin in external location as expected. In Plugin_Context there is Like in
May be we should fix |
Thanks @ernilambar for your feedback. I've detected that problem, and I've committed a fix. Update the PR and it should work. |
Co-authored-by: Mukesh Panchal <[email protected]>
None, it's working |
What we need for the submission form from wordpress.org is run static checks in an arbitrary path. It's helpful as well for any developer user to directly run static checks in any directory.
Resolves #478