WWW-www.enlightenment.org pushed a commit to branch master. http://git.enlightenment.org/website/www-content.git/commit/?id=03a1f6cd9c488bec31b33be5e2c5db11d15a5286
commit 03a1f6cd9c488bec31b33be5e2c5db11d15a5286 Author: Mike Blumenkrantz <[email protected]> Date: Tue Nov 21 07:09:06 2017 -0800 Wiki page git-guide.md changed with summary [] by Mike Blumenkrantz --- pages/contrib/devs/git-guide.md.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/contrib/devs/git-guide.md.txt b/pages/contrib/devs/git-guide.md.txt index 612ae211..98bfaa39 100644 --- a/pages/contrib/devs/git-guide.md.txt +++ b/pages/contrib/devs/git-guide.md.txt @@ -143,7 +143,7 @@ $ git push origin --delete devs/{devname}/{branch} ### Feature Branches ### -Anyone with full commit access can create, manage, or delete a feature branch for a repository. The naming must be ``feature/{name}`` where ``{name}`` is the name of the feature. Feature branches can be pushed to by anyone with any form of commit access, but they cannot be rewritten (ie. no ``rebase -i``). +Anyone with full commit access can create, manage, or delete a feature branch for a repository. The naming must be ``feature/{name}`` where ``{name}`` is the name of the feature. Feature branches can be pushed to by anyone with any form of commit access (including probies), but they cannot be rewritten (ie. no ``rebase -i``). The purpose of a feature branch is to continue the collaborative development of a feature which has already reached the state of being functional during initial development in a developer branch; feature branches should be considered the "alpha release" state for any significant feature prior to merging it to master. --
