This is a very short example which does not showcase all of the features of GitHub Actions, but it provides a peek into the structure of the configuration file.

The uses keyword tells the script what action to enact.

Each job can have many phases which are grouped together by the steps keyword.

The runs-on command tells GitHub which runner will execute this job (this is a virtual server and you can choose between Windows/Mac/Linux).

We start a list of tasks (jobs) that should happen once this action is triggered.

We signify when this action should run (when a pull request is opened).

We give a name to our action (My GitHub Action).

This configuration file is in YAML format (.yml) and an example looks like this: name: My GitHub Action At its core, an action is a configuration file that has a list of commands that describe: GitHub Actions are commands we can trigger when something happens in our repository. Plus, we don’t want to bum out our colleagues.

So to whom should we pass along these tasks? Another coworker? They can just pass it along to someone else and it won’t free up anyone’s time.

Building and publishing the application.

Making sure the application compiles when merging new code.

If you've ever developed an Android application, you know how tedious some tasks can get:

That way, you can have more time to do things you want to do. And they can be a bit boring, difficult, and monotonous.īut instead of laboring away at those daily tasks, you can delegate them so someone or something else does them for you. There are many repetitive tasks that we have to do every day.

Add android studio project to github