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 ArkGameFrame better.
There are three main branches here:
-
masterbranch.(1). It is the latest (pre-)release branch. We use
masterfor tags.(2). Don't submit any PR(Pull Request) on
masterbranch. -
developbranch.(1).There is a
developforArkGameFramedeveloping version. It is our stable developing branch. After full testing,developbranch will be merged tomasterbranch for the next release.(2). You are recommended to submit bugfix or feature PR on
developbranch.
Normal bugfix or feature request should be submitted to develop branch. After full testing, we will merge them to master branch for the next release.
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
masterordevelop. - Update code or documentation if you have changed APIs or important functions.
- 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
developbranch.
Try to be similar with the other authers.
By contributing to ArkGameFrame, you agree that your contributions will be licensed
under Apache LICENSE