-
Notifications
You must be signed in to change notification settings - Fork 46
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
[Question] Static Test action support custom Path #36
Comments
Thanks for the suggestion. Just for clearity, which GitHub action are you referring to? I guess the PHPStan version because the PHPCS action does not use composer or Magento or anything - it just installs PHPCS and runs it ... If you could share your setup it would be helpful I guess. |
I Mean the phpcs one for example the default one
if you get a git repo for a magento project and not a module you will get some "false" report (like not what I expect) my goals is to run phpcs only on app/code/ folder by doing something like Updating the action.yml like that
and then update the entrypoint like
and finally be able in the project repo to add the workflow like
i hope it's more clear ? I made a "quick & dirty" test by changing the docker image (by forking your's) and got my use case working as expected. Not sure if relevant for everyone but usefull on our case :) Thanks |
Hi,
I'm currently got some Magento repo with custom code on "app/code".
My goal is to be able to make the Github action Static test execute only on app/code...
By default it's not supported by your nice setup.
I was thinking adding a parameter like there is for the standard, but for the "path to scan" and after if not empty analyze that folder.
Do you think it's the "good way" to go ? thanks
The text was updated successfully, but these errors were encountered: