1
0
Fork 0

Merge pull request #3775 from rantonmattei/patch-1

VCS section: add requirements for the branch name
pull/3772/merge
Jordi Boggiano 2015-02-25 16:53:56 +00:00
commit 475c84d4b1
1 changed files with 1 additions and 1 deletions

View File

@ -234,7 +234,7 @@ 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. For version constraint naming conventions see point to your custom branch. Your custom branch name must be prefixed with `"dev-"`. For version constraint naming conventions see
[Libraries](02-libraries.md) for more information. [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: