Question 1

How do I run phpqa in GitHub Actions?

Accepted Answer

Use the Docker container in your workflow YAML, mounting your project directory. The README provides basic commands; for GitHub Actions, you'll need to set up a step with docker run and appropriate volume mounts to integrate with your codebase.

Question 2

phpqa vs installing tools individually with composer – which is better?

Accepted Answer

phpqa is better for consistency and ease in CI/CD, as it avoids dependency conflicts and setup time. However, manual installation offers more control over tool versions and configurations, which might be necessary for specific project needs.

Question 3

Does phpqa include the latest versions of PHPStan and Psalm?

Accepted Answer

Yes, the daily updated tags ensure tools are current, but you should check the specific image tag or the tools table in the README to confirm compatibility with your PHP version, as some versions may lag.

Question 4

How can I add a custom tool that's not in phpqa?

Accepted Answer

You cannot directly add tools to the pre-built image; instead, you need to extend the Dockerfile or run the tool separately outside the container, which undermines the all-in-one convenience.

Question 5

What's the performance impact of using phpqa?

Accepted Answer

There's a slight overhead due to Docker containerization, which can increase run times compared to native installations. However, for most CI/CD pipelines, the consistency benefits outweigh this minor delay.

Question 6

Is phpqa suitable for Laravel projects?

Accepted Answer

Yes, it includes Larastan and other Laravel-specific tools like pint, making it a good fit. Ensure you use the appropriate PHP version tag that supports these tools, as listed in the README table.

phpqa - jakzal

What is phpqa - jakzal?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions