This repository is used to manage all swoft components.
All components will NOT be modified in the original repository of component, SHOULD ALWAYS be modified in this repository, also commit and push to this repository, and then @swoft-bot would sync changes to the original repository of component by git subtree push
, notice that this action needs triggered by the repositories owner.
git subtree add --prefix=src/[folder] [repository] [ref] --squash
Note that
--squash
option is required.
e.g. Add swoft/pipeline component as a Sub Repository,
git subtree add --prefix=src/pipeline git@github.com:swoft-cloud/swoft-pipeline master --squash
Just use git commit
as usual, and Push to this repository
git subtree push --prefix=src/[folder] [repository] [ref] --squash
Note that
--squash
option is required.
e.g. Add swoft/pipeline component as a Sub Repository
git subtree push --prefix=src/pipeline git@github.com:swoft-cloud/swoft-pipeline master --squash
Tips: You could use
remote
to instead of[repository]
property for easier to use. e.g. AddRemote
first,git remote add -f pipeline git@github.com:swoft-cloud/swoft-pipeline.git
, after this, you could usepipeline
instead of[repository]
, for examplegit subtree push --prefix=src/pipeline pipeline master --squash
After Sync changes to the Original Repository of Component
, you just need to Release a new version in the original repository of component.
We do NOT suggest modifying code in the original repository, but if you do, you could use the command below to merge it.
git subtree pull --prefix=src/[folder] [repository] [ref] --squash
Note that
--squash
option is required.
e.g. Pull swoft/pipeline repository into src/pipeline
git subtree pull --prefix=src/pipeline git@github.com:swoft-cloud/swoft-pipeline master --squash
phpunit
// output coverage. require xdebug ext
phpunit --coverage-text
// output coverage without xdebug
phpdbg -dauto_globals_jit=Off -qrr /usr/local/bin/phpunit --coverage-text
only tests an special component:
php run.php --testsuite event