瀏覽代碼

* 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

rkerner 10 年之前
父節點
當前提交
38d546da45
共有 1 個文件被更改,包括 4 次插入0 次删除
  1. 4 0
      doc/04-schema.md

+ 4 - 0
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
 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.
 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:
 An example:
+
 If you have a testing branch, that is heavily maintained during a testing phase and is
 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`.