From 38d546da453762c37ee19e6ee9f4f59ce4af5b74 Mon Sep 17 00:00:00 2001 From: rkerner Date: Wed, 11 Feb 2015 16:03:17 +0100 Subject: [PATCH] * added non-feature-branches to handle non-numeric branches matching configured patterns not been handled as feature branches * added documentation to doc/04-schema.md * fixed indentation and styling --- doc/04-schema.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/04-schema.md b/doc/04-schema.md index b0b904687..dc68f6963 100644 --- a/doc/04-schema.md +++ b/doc/04-schema.md @@ -799,7 +799,11 @@ To handle non-numeric named branches as versions instead of searching for a pare with a valid version or special branch name like master, you can set patterns for branch names, that should be handled as dev version branches. +This is really helpful when you have dependencies using "self.version", so that not dev-master, +but the same branch is installed (in the example: latest-testing). + An example: + If you have a testing branch, that is heavily maintained during a testing phase and is deployed to your staging environment, normally "composer show -s" will give you `versions : * dev-master`.