public-mirrors
/
composer
mirror of https://github.com/composer/composer
1
0
Fork 0
Code

* 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
pull/3699/head
rkerner 2015-02-11 15:59:26 +01:00
parent a8b8a2e143
commit 62636cdd64
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/04-schema.md
View File

@ -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. names, that should be handled as dev version branches.
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".
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-.*"] "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. Optional.