For your workflow, let’s name the job “ deploy” here The name of each job should be unique, or you can provide a unique job id at the job_id key. This can be a single event string or array of events string or event types. on defines names of the events which will trigger the workflow.GitHub will automatically detect the workflow files.

Inside this folder, you will put workflow files. github folder in your project root, and inside that, create a workflows folder. You may need to execute other tasks like handling secrets in the workflow, creating temporary files to support the project etc.īefore completing the steps, you need to create the workflow file first. Install dependencies to support Ruby project (which is actually Fastlane project) using Bundler.Summary of steps that you’re going to do in GitHub action is as follows: You will use GitHub action to set up the environment to run Fastlane tasks. Please read those posts before this if you search for the complete guideline to start CI/CD for your Android project. Previously I’ve written part 1, where I showed the initial setup process, and part 2 showed Fastlane integration. This is the last(!) part of this series of posts.

Setting up github android studio 2012