Skip to content
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

Merged
merged 3 commits into from Oct 15, 2021

Conversation

greg0ire
Copy link
Member

No description provided.

@greg0ire greg0ire changed the title Setup Psalm Setup Psalm and reuse upstream workflows Oct 15, 2021
@@ -0,0 +1,15 @@
<?xml version="1.0"?>
<psalm
errorLevel="7"
Copy link
Member

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) ?

Copy link
Member

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.

Copy link
Member Author

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.

Copy link
Member Author

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.

@greg0ire greg0ire merged commit d13947c into doctrine:1.13.x Oct 15, 2021
@greg0ire greg0ire deleted the setup-psalm branch October 15, 2021 21:08
@greg0ire greg0ire added this to the 1.13.3 milestone Jul 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants