Bruce Weirdan 62e7e7f470 Reorganize pushes to psalm/phar ... Previously we built phar and pushed it: 1. To `psalm/phar:master` (always) 2. To `psalm/phar:$tag` (for tagged releases) However it's entirely possible to tag branches that diverged from master (like when we do a patch release for a legacy version). In this case our push to `psalm/phar:master` was rejected and script failed. As a result, `psalm/phar` was missing the tag (release). Now we will either: * push to `psalm/phar:master` (if the build was for `vimeo/psalm:master`) * or push to `psalm/phar:$tag` (if it's a tagged release)		2023-02-24 21:47:11 -04:00
..
build-phar.sh	Disable parallel PHAR build	2022-11-26 00:36:47 -04:00
composer-require-checker-config.json	Added Composer\Audoload\ClassLoader, it is soft dependency symbol	2022-02-11 22:51:31 +01:00
generate_issues_list_doc.php	Fix code style.	2022-01-12 15:33:26 -06:00
generate_levels_doc.php	Import instead of using fqn	2021-12-03 20:11:20 +01:00
generate_testsuites.php	Require trailing commas	2022-12-18 13:20:31 -06:00
github-deploy-phar.sh	Reorganize pushes to psalm/phar	2023-02-24 21:47:11 -04:00
improve_class_alias.php
max_used_shortcode.php	Require trailing commas	2022-12-18 13:20:31 -06:00
phar.psalm.xml	remove usage of totallyTyped internally	2022-02-12 09:51:06 +01:00
test-with-real-projects.sh	List refactoring v5 (#8820)	2022-12-13 21:40:19 +01:00
tests-github-actions.sh	Workaround for PHPUnit process isolation issue with composer 2.2	2021-12-23 22:44:49 +02:00
update-property-map.php	Require trailing commas	2022-12-18 13:20:31 -06:00