We have PHPUnit required in composer.json, why not phan also? It's run on CI, so it should be readily available for devs to run before they request review. Why require devs to install it separately globally, and make sure their version matches the version on CI so that get useful results?
|integration/config : master||docker: [mediawiki-phan] Fix phan version validation|
|integration/config : master||docker: [mediawiki-phan] Fix syntax error in shell scripts|
|integration/config : master||jjb: Move mediawiki-core-php72-phan-docker, mwext-php72-phan-docker to new image|
|mediawiki/tools/phan : master||Move phan/phan to composer require and upgrade it|
|integration/config : master||docker: [mediawiki-phan] Allow repos to require phan like normal|
|Resolved||Daimona||T220589 Support phan in MediaWiki's default composer.json|
|Resolved||Jdforrester-WMF||T192166 Drop HHVM support from MediaWiki|
|Resolved||Jdforrester-WMF||T234062 ci-src-setup job (used by mediawiki-core-php72-phan-docker) is still running on PHP 7.0.33|
|Resolved||Jdforrester-WMF||T234384 Drop HHVM from CI|
|Open||jijiki||T229792 Remove HHVM from production|
|Open||awight||T236019 Remove HHVM support from Quibble|
|Open||jijiki||T236048 Move debugging symbols and tools to a new class|
Because phan requires PHP >=7.0 (other dev deps require >=5.6.99) and until recently also required specific versions of php-ast, which would have make composer install really inconvenient for a lot of people.
I think we can reconsider this and implement it after core requires PHP >=7.0.
OK, this is done from the CI end, right? We now "just" need to do a release of mediawiki-phan-config with the dependency and then remove the 'extra' field when bumping all the repos to the new release?