From 40b498c96e5208df324d31088ac35dba78c258dc Mon Sep 17 00:00:00 2001 From: rkerner Date: Wed, 11 Feb 2015 16:01:41 +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 | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/doc/04-schema.md b/doc/04-schema.md index 0fd8fd6ed..b0b904687 100644 --- a/doc/04-schema.md +++ b/doc/04-schema.md @@ -801,7 +801,7 @@ names, that should be handled as dev version branches. 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". +deployed to your staging environment, normally "composer show -s" will give you `versions : * dev-master`. If you configure latest-.* as a pattern for non-feature-branches like this: @@ -809,8 +809,7 @@ If you configure latest-.* as a pattern for non-feature-branches like this: "non-feature-branches": ["latest-.*"] } -Then "composer show -s" will give you "versions : * dev-latest-testing". - +Then "composer show -s" will give you `versions : * dev-latest-testing`. Optional.