Skip to content
Browse files

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.
  • Loading branch information...
1 parent fb62e2b commit 1ca478de859617111134496c27531d52e6a880d6 Ben Waine committed Aug 15, 2012
Showing with 2 additions and 1 deletion.
  1. +2 −1 doc/
3 doc/
@@ -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
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
-point to your custom branch.
+point to your custom branch. For version constraint naming conventions see
+[Libraries]( for more information.
Example assuming you patched monolog to fix a bug in the `bugfix` branch:

0 comments on commit 1ca478d

Please sign in to comment.
Something went wrong with that request. Please try again.