-
Notifications
You must be signed in to change notification settings - Fork 236
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
Setup Psalm and reuse upstream workflows #430
Conversation
@@ -0,0 +1,15 @@ | |||
<?xml version="1.0"?> | |||
<psalm | |||
errorLevel="7" |
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.
isn't it quite high as level (knowing that for psalm, higher levels are less strict) ?
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.
I assume, @greg0ire wants to start easy, so we can iterate further once the CI job is in place.
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.
I let Psalm pick the level itself with psalm --init
. Level 6 finds 40 errors, which would make this PR a bit fat IMO.
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.
Yes exactly @derrabus . Also, this allows me to reuse all upstream workflows: the static analysis workflow cannot be reused if we don't have Psalm in the project.
No description provided.