Spring is in the air, which means a lot of new things are on the horizon. Flowers will bloom, animals will give birth, and the landscape will change as the season shifts from one into another. However, Nature is not the only thing experiencing changes at this time; AppFlower is also experiencing many changes as we prepare a number of tools for improved collaborations.
Recently, we’ve decided to switch from SVN (Apache Subversion) to GitHub. While they have similarities, there are a few reasons we believe the switch will improve the work flow:
- 1. GitHub makes it easier for developers to contribute to projects, without needing direct write-access to the main repository. With forks, you can easily make a private copy of the project and extend it however you want. We appreciate good ideas and suggestions, so please use GitHub’s pull request feature to send us feedback.
- 2. GitHub allows the distribution of work, while SVN requires a centralized location for storage. This makes the creation of local commits possible, before pushing back to the GitHub hosted project.
- 3. GitHub improves social coding on Open Source projects, with features like: following friends, watching projects, in-line code commenting, and discussions on pull requests.
The practical work flow of GitHub and the commands used are a bit different than those of SVN; however, you can find a nice crash-course in the GitHub help section. We’ve also updated our How-To Playground with GitHub commands, so the transition should go much easier for you. If you have any questions, you can always post on the forum, or contact support for more information.
In the meantime, check out our Public Repositories on GitHub.com!
Add Your Comment