It takes time to master highly specialized and complex IT domains like software development and automation. But with time at a premium, you would often be required to deliver projects quickly. So, what do you do in that case? You look for simple solutions, right.

If you are tired of searching for easy-to-execute and straightforward steps to run the Github Actions Workflow, this post is for you. Because time is at a premium, we won't waste any more of it. Let's dive straight into the discussion.

Before we start, let's quickly look at a hypothetical Github Actions Workflow command screen that we will use as an illustration to help you better understand the steps involved.

           go-version: '1.9.3' # The Go version to download (if necessary) and use.

           OUTPUT=$(go run main.go | tail -1) &&

           echo "::set-output name=OUTPUT::$OUTPUT"

         if: steps.main.outputs.OUTPUT == 0

           cd ./mainRepository/projectA &&

         if: steps.main.outputs.OUTPUT == 1

           cd ./mainRepository/projectB &&

First things first. Just like there must be a car to learn how to drive a car, there must be a workflow to learn how to run a workflow.

In the example above, we have first defined a workflow that runs on a 'push' event. We have divided it into Project A and Project B and assigned it to the latest version of an Ubuntu container. Because our main program only calculates a value equal to 0 or 1, we can also call it a flip-coin program. If the toss of the coin yields 0, we run Project A. If the coin yields 1, we run Project B. Simple, isn't it?

   s1 := rand.NewSource(time.Now().UnixNano())

The only command inside Project A and B is the 'Print' command, indicating which routine is currently being run.

Alright. We now have the car. It is time now to understand the steps involved in driving it.

The first step is to check the main repository in the ./mainRepository folder and then install the ‘Go-version 1.9.3’ to run the main program.

The next step is to run the main repository. To do so, we first assign it the ID 'main' that will help us retrieve the output later. The other half of this step involves defining the output of the program. Once done, our next action is to let Github Actions know the OUTPUT variable will be the output obtained by running the main repository.

The last step is to define an ‘if’ statement to determine which project to run based on the value or output obtained from our flip-coin program. You can do so by linking the string 'steps. {step_name}.outputs.{step_output}'.

In this post we can talk about steps to run the Github Actions Workflow, 

flip coin program

Trending Blogposts on flip coin program

'If' Statements on Github Actions

Popular Discussions on flip coin program

PRODUCTS

QUICK LINKS

LEGAL

flip coin program

Trending Blogposts on flip coin program

'If' Statements on Github Actions

Popular Discussions on flip coin program