Welcome to create Pull Requests or open Issues for bugfix, doc, example, suggestion and anything.
master
↑
dev <--- PR(hotfix/typo/3rd-PR)
↑ PR
{domain}-feature-{date}
Weex Branches
masterbranch 0.masteris the latest (pre-)release branch.devbranch 0.devis the stable developing branch. Github Release is used to publish a (pre-)release version tomasterbranch. 0. It's RECOMMENDED to commit hotfix (like typo) or feature PR todev.{domain}-feature-{date}branch 0. The branch for a developing iteration, e.g.android-feature-20160607is an android developing iteration which is done at 2016.06.07.{domain}consists ofandroid,ios,jsfmandhtml5. 0. DO NOT commit any PR to such a branch.
{module}-{action}-{shortName}
{module}, see commit log module{action}feature: checkout from{module}and merge to{module}later. If{module}not exists, merge todevbugfix: likefeature, for bugfix onlyhotfix: checkout frommasteror releasetag, merge tomasterand{module}later. If{module}not exists, merge todev
for example:
android-bugfix-memoryjsfm-feature-communicationandroid-hotfix-compute-layout
{action} [{module}] {description}
{action}+add*update or bugfix-remove
{module}- Including: android, ios, jsfm, html5, component, doc, website, example, test, all
{description}- It's RECOMMENDED to close issue with syntax
close #123orfix #123, see the doc for more detail. It's useful for responding issues and release flow.
- It's RECOMMENDED to close issue with syntax
for example:
+ [android] close #123, add refreshing for WebView* [doc] fix #123, update video auto-play property- [example] remove abc
In order to contribute code to Weex, you (or the legal entity you represent) must sign the Contributor License Agreement (CLA).
You can read and sign the Alibaba CLA online.
For CLA assistant service works properly, please make sure you have added email address that your commits linked to GitHub account.
Please read How to setting your Email address in Git and How to adding an email address to your GitHub Account.
- Tabs for indentation(not spaces)
*operator goes with the variable name (e.g. Type *variable;)- Function definitions: place each brace on its own line.
- Other braces: place the open brace on the line preceding the code block; place the close brace on its own line.
- Use
#pragma marksto categorize methods into functional groupings and protocol implementations - Follow other guidelines on GitHub Objective-C Style Guide
- Use Google Java Style as basic guidelines of java code.
- Follow AOSP Code Style for rest of android related code style.