From 8695fd69486703e371d37120d8a1f8fb9c5ad29d Mon Sep 17 00:00:00 2001 From: Dane Powell Date: Tue, 5 Dec 2017 11:15:17 -0800 Subject: [PATCH] Clarified language on branch naming for forks --- doc/05-repositories.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/05-repositories.md b/doc/05-repositories.md index ad2a04b45..1aaadf4c8 100644 --- a/doc/05-repositories.md +++ b/doc/05-repositories.md @@ -205,8 +205,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. Your custom branch name must be prefixed with -`"dev-"`. For version constraint naming conventions see +point to your custom branch. In `composer.json`, you should prefix your custom +branch name with `"dev-"`. 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: