Barney Laurance d44be5eb9c Allow deploying phar to any github repository ... Potentially useful for fork owners to test out phar deployment without affecting the official psalm/phar repo. To enable phar deployments from your own fork of psalm: - Enable builds with Travis - Create a github repository to hold recieve the built phar packages - Create a new dedicated github user for the deployments - From your main github account, invite the new user to collobrate on the phar repository - From the new user's account, accept the invitation - From the new user's account, obtain a 'new personal access token' ( https://github.com/settings/tokens/new ) with repo scope - In travis settings for your fork of psalm, set two environment variables: - PHAR_REPO_SLUG - this should be the name the phar repo you set up earlier, e.g. fred/phar - GITHUB_TOKEN - This is the personal access token of the new user you obtained above. Anyone who knows this token can push to the repository, so keep it secret. Make sure 'Display value in build log' is switched off' Now any push to branches in your fork of psalm, should automatically result in a commit containing the phar file in your phar repository.		2019-06-08 09:46:08 -04:00
..
build-phar.sh	Exit build-phar script on any error	2019-06-07 06:52:07 -04:00
phar.psalm.xml	Plugin interface segregation (#1076)	2018-11-12 11:20:59 -05:00
travis-deploy-phar.sh	Allow deploying phar to any github repository	2019-06-08 09:46:08 -04:00
travis-php-cs-fixer.sh	Support the pylint output format	2018-02-19 22:35:48 -05:00