Welcome to report Issues or pull requests. It's recommended to read the following Contributing Guide first before contributing.
We use Github Issues to track public bugs and feature requests.
Please search the existing issues to see if any similar issue or feature request has already been filed. You should make sure your issue isn't redundant.
If you open an issue, the more information the better. Such as detailed description, screenshot or video of your problem, logcat or code blocks for your crash.
We strongly welcome your pull request to make Tinker better.
There are three main branches here:
masterbranch.- It is the latest (pre-)release branch. We use
masterfor tags, with version number1.1.0,1.2.0,1.3.0... - Don't submit any PR on
masterbranch.
- It is the latest (pre-)release branch. We use
devbranch.- It is our stable developing branch. After full testing,
devwill be merged tomasterbranch for the next release. - You are recommended to submit bugfix or feature PR on
devbranch.
- It is our stable developing branch. After full testing,
hotfixbranch.- It is the latest tag version for hot fix. If we accept your pull request, we may just tag with version number
1.1.1,1.2.3. - Only submit urgent PR on
hotfixbranch for next specific release.
- It is the latest tag version for hot fix. If we accept your pull request, we may just tag with version number
Normal bugfix or feature request should be submitted to dev branch. After full testing, we will merge them to master branch for the next release.
If you have some urgent bugfixes on a published version, but the master branch have already far away with the latest tag version, you can submit a PR on hotfix. And it will be cherry picked to dev branch if it is possible.
master
↑
dev <--- hotfix PR
↑
feature/bugfix PR
The code team will monitor all pull request, we run some code check and test on it. After all tests passed, we will accecpt this PR. But it won't merge to master branch at once, which have some delay.
Before submitting a pull request, please make sure the followings are done:
- Fork the repo and create your branch from
masterorhotfix. - Update code or documentation if you have changed APIs.
- Add the copyright notice to the top of any new files you've added.
- Check your code lints and checkstyles.
- Test and test again your code.
- Now, you can submit your pull request on
devorhotfixbranch.
Use Code Style for Java and Android.
- 4 spaces for indentation rather than tabs
By contributing to Tinker, you agree that your contributions will be licensed under its BSD LICENSE