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

VCS section: add requirements for the branch name 

If you want to use a custom branch in your requirements in your `composer.json`, that branch must be prefixed with "dev-" or you'll get an error:
```sh
[UnexpectedValueException]
  Could not parse version constraint some-branch: Invalid version string "some-branch".
```

It took me a while to find that info, so I figured I'd rather edit the doc.
Let me know.
pull/3775/head
Raphael Antonmattei 2015-02-25 11:46:36 -05:00
parent 3ba581f0df
commit 7b635f835d
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/05-repositories.md
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: