From 62636cdd64b9e1653e617605fec90c9f8f1d0a2c Mon Sep 17 00:00:00 2001 From: rkerner Date: Wed, 11 Feb 2015 15:59:26 +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 --- doc/04-schema.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/04-schema.md b/doc/04-schema.md index a7be21766..6c0a42116 100644 --- a/doc/04-schema.md +++ b/doc/04-schema.md @@ -802,16 +802,16 @@ with a valid version or special branch name like master, you can set patterns fo 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". +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". - If you configure latest-.* as a pattern for non-feature-branches like this: +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. \ No newline at end of file