1
0
Fork 0

Merge pull request #1003 from benwaine/documentation_clarification

Added a small clarification to the 05-repositories article.
pull/1000/merge
Jordi Boggiano 2012-08-15 04:00:22 -07:00
commit 2d670fc5cb
1 changed files with 2 additions and 1 deletions

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: