Repository navigation
Replies: 5 comments 12 replies
|
Can you tell us more? How exactly would that change things for the end user? |
|
The command will look something like that |
|
It appears we already ship a docker image at https://hub.docker.com/r/vimeo/psalm-github-actions (repo: https://github.com/psalm/psalm-github-actions). Can't we reuse that repo instead? |
|
I would love to have an official Psalm Docker image (with latest or various versions of PHP, Composer, Psalm) that I could use in a BitBucket Pipeline. Or would love to have an official BitBucket Pipeline similar to the GitHub Action above. |
|
Created pull request |
Uh oh!
There was an error while loading. Please reload this page.
I suggest adding the creation of a docker image for the psalm.
It will decouple a project from psalm dependency and allow to use of the latest version of the psalm even when there is a conflict with composer dependency.
I can automate this process but need feedback first. Will it be beneficial to others? And how do the authors think about it?
All reactions