At this point, teams will begin to explore what CI/CD options are out there, recognizing that establishing a robust CI/CD pipeline will improve the consistency, reliability, and quality of their development and release process.

But as team size grows and the need for more frequent and predictable releases arises, many teams realize that building APKs/AABs off an individual’s machine just doesn’t scale. For many indie devs and small teams, using Android Studio or Gradle for this gets the job done without too much of a fuss. Many Android devs will at some point in their careers be responsible for building and uploading an APK or AAB to the Google Play Console. GitHub will now create a remote repository, ready and waiting for your first commit.Setting up a CI/CD pipeline is critical for scaling your development and release process to match rapid growth in team size and maturity.

When you’re happy with the information you’ve entered, click “Create Repository.”.

Since we’ll be creating this file manually, make sure you leave “Initialize this repository” deselected.

You now have the option to automatically generate an empty README file, by selecting the “Initialize this repository” checkbox.

Unless you have a specific reason not to, you should make your repository public so that other people can download it, and perhaps even contribute to your project at some point.

Decide whether your repository should be public, or private.

Give your repository a name and provide a description.

In GitHub’s toolbar, select the “+” icon, followed by “New Repository.”.

In your web browser, head over to and log into your GitHub account, if you haven’t already.

We can complete this task without issuing any Git commands, by using the website: Let’s start by creating a remote repository.

Connect android studio to github