Atlas Contributing Guide

Atlas Branches

1. branch
   1. master is the latest (pre-)release branch.
2. dev branch
   1. It’s RECOMMENDED to commit hotfix (like typo) or feature PR to dev.
3. {domain}-feature-{date} branch
   1. The branch for a developing iteration, e.g. core-feature-20170118 is an atlas-core developing iteration which is done at 2017.01.18. {domain} consists of core, update, plugin and aapt.
   2. DO NOT commit any PR to such a branch.

• , see commit log module
• {action}
  • feature: checkout from {module} and merge to {module} later. If {module} not exists, merge to dev
  • bugfix: like feature, for bugfix only

for example:

• core-bugfix-memory
• plugin-feature-redex
• update-hotfix-sequence

• {module}
  • Including: atlas-core, atlas-aapt, atlas-update, atlas-gradle-plugin, atlas-doc, atlas-website, atlas-demo, test, all
• {description}
  • It’s RECOMMENDED to close issue with syntax close #66 or fix #66, see for more detail. It’s useful for responding issues.

• [all] close #66, add refreshing for memory
• [atlas-demo] remove abc

Create Pull Requests.

In order to contribute code to Atlas, you (or the legal entity you represent) must sign the Contributor License Agreement (CLA).

For CLA assistant service works properly, please make sure you have added email address that your commits linked to GitHub account.

Please read and How to adding an email address to your GitHub Account.