public-mirrors
/
composer
mirror of https://github.com/composer/composer
1
0
Fork 0
Code

Added a small clarification to the 05-repositories article to 

make it clearer how to use version constraints when making use
of your own VCS repository.
pull/1003/head
Ben Waine 2012-08-15 11:04:32 +01:00
parent fb62e2b52f
commit 1ca478de85
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
doc/05-repositories.md
View File

@ -161,7 +161,8 @@ project to use the patched version. If the library is on GitHub (this is the
case most of the time), you can simply fork it there and push your changes to case most of the time), you can simply fork it there and push your changes to
your fork. After that you update the project's `composer.json`. All you have your fork. After that you update the project's `composer.json`. All you have
to do is add your fork as a repository and update the version constraint to to do is add your fork as a repository and update the version constraint to
point to your custom branch. point to your custom branch. For version constraint naming conventions see
[Libraries](02-libraries.md) for more information.
Example assuming you patched monolog to fix a bug in the `bugfix` branch: Example assuming you patched monolog to fix a bug in the `bugfix` branch: