Raphael Antonmattei 7b635f835d 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.		2015-02-25 11:46:36 -05:00
..
articles	Tweak satis/toran/packagist docs	2015-02-24 12:49:14 +00:00
dev	Typo fixes	2012-06-20 14:15:54 -07:00
faqs	Update why-are-unbound-version-constraints-a-bad-idea.md	2015-02-17 02:46:15 +01:00
fixtures	Update fixtures to include gar/nix (which is being replaced) and bar/baz (which has a branch-alias)	2014-10-13 12:55:00 +02:00
00-intro.md	Improve notice about /usr/local/bin	2015-01-28 21:33:42 -05:00
01-basic-usage.md	I think 'dump-autoload' command is more proper.	2015-01-28 15:07:44 +09:00
02-libraries.md	Update documententation for version shorthand parsing	2015-01-20 09:05:40 +01:00
03-cli.md	Updated documentation	2015-02-03 15:26:02 +01:00
04-schema.md	Merge pull request #3699 from trivago/non_feature_branches	2015-02-14 15:44:45 +00:00
05-repositories.md	VCS section: add requirements for the branch name	2015-02-25 11:46:36 -05:00
06-community.md	Add user ml link	2012-10-24 10:22:40 +02:00