enlightenment/www-content
enlightenment
/
www-content
6
0
Fork 2
Code Issues Pull Requests Projects Releases Wiki Activity

Wiki page git-guide.md changed with summary [add feature branch usage] by Mike Blumenkrantz

This commit is contained in:
Mike Blumenkrantz 2017-11-20 07:25:36 -08:00 committed by apache
parent 30062c008d
commit 18c462c3bd
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
pages/contrib/devs/git-guide.md.txt
View File

@ -165,6 +165,16 @@ Pass the ``--delete`` option to ``git-push`` to delete a developer branch:
$ 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``).
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.
Feature branches will be automatically built by jenkins, and any build failures will be emailed to everyone who has any commits in the branch.
Creating and managing feature branches is identical to the management of developer branches with only the name of the branch being changed.
## Developer Repositories ##
If you are starting a new project, or just trying something out that doesn't belong to any of the existing repositories, you can create your own developer repository.