Deploying Android Apps Using GitHub Actions

May 4 2023 · Kotlin 1.7.21, Android 13, Android Studio Electric Eel

Part 1: Automate Releases with GitHub Actions

05. Trigger a Workflow

Episode complete

Play next episode

About this episode

Leave a rating/review

See forum comments
Cinema mode Mark complete Download course materials
Previous episode: 04. Generate a Signed Build Next episode: 06. Authenticate Firebase Project

Get immediate access to this and 4,000+ other videos and books.

Take your career further with a Kodeco Personal Plan. With unlimited access to over 40+ books and 4,000+ professional videos in a single subscription, it's simply the best investment you can make in your development career.

Learn more Already a subscriber? Sign in.

Heads up... You've reached locked video content where the transcript will be shown as obfuscated text.

You want to release a build in the following scenarios:


Trigger Based on a Version Tag

A version tag name usually has the v prefix. For example, v1.10, v0.31, v/3.31 etc. You’ll use this convention to trigger the workflow when you push a version tag.

      - 'v*'
git tag v0.1 -a -m "Release v0.1"
git push origin master --follow-tags
git commit --allow-empty -m "Empty commit"
git push origin master

Trigger Based On A Pull Request to Master

A typical workflow among teams is to send a release APK to the QA team whenever a developer creates a PR to the master branch. Your next step is to make this happen automatically.

      - master

Preventing a Merge if Tests Fail

Before merging any code to master, you want to make sure that the new code builds correctly and that all tests pass. If any of these conditions fail, you want to block the pull request from merging. Branch protection helps you do this.