This is where hosted sites like GitHub really help, because they allow you to keep a backup of all of your precious code files, ready to be recalled in case of disk crashes, equipment loss, or any number of other pitfalls.

The downside of all this automation in integrated development environment tools is that it creates a lot of files, and keeping track of them (and the changes that get made to them) can be a big headache. It took Android Studio only a few moments to construct it, and then we had a project folder complete with build scripts, app code, and layout files. If you look back at the code in our last installment, it was very basic. With that, let’s connect the IDE with our hosted source control provider.

This only means that if you choose to go your own way with something other than GitHub as your source control tool of choice, then we’ll leave it as an exercise for you, dear reader, to complete and let us know how it goes in the ODROID forums. The good news for Android Studio is that it treats GitHub as a first-class source code repository host, that is to say, you can make other hosted Git providers work, but it’s just not quite as slick.

There are several Git-based choices in the marketplace, but for our purposes, we will use GitHub for this column, with the upside being that all of the projects, and mistakes, will be available to the community to view, give comments, and improve. As mentioned previously, the 800-pound gorilla of online open source projects is GitHub. Welcome back, appdev initiates! If you’re like me, you’re more than ready to increase your app development skills.

How to push to github android studio