From 1ca478de859617111134496c27531d52e6a880d6 Mon Sep 17 00:00:00 2001 From: Ben Waine Date: Wed, 15 Aug 2012 11:04:32 +0100 Subject: [PATCH] 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. --- doc/05-repositories.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/05-repositories.md b/doc/05-repositories.md index 24dbf3782..de9f29ffa 100644 --- a/doc/05-repositories.md +++ b/doc/05-repositories.md @@ -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](02-libraries.md) for more information. Example assuming you patched monolog to fix a bug in the `bugfix` branch: