GitHub Actions basics - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the event that triggers the GitHub Action workflow.

Git

on: [1]

Drag options to blanks, or click blank then click option'

Apull

Bcommit

Cpush

Dmerge

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'commit' instead of 'push' as the event name.

Using 'merge' which is not a valid event keyword here.

The push event triggers the workflow when code is pushed to the repository.

2fill in blank

medium

Complete the code to define the job name in the workflow.

Git

jobs:
  build:
    [1]: ubuntu-latest

Drag options to blanks, or click blank then click option'

Aruns

Bruns-on

Cruns-on-ubuntu

Druns-on-latest

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'runs' instead of 'runs-on'.

Adding extra words like 'runs-on-ubuntu' which is invalid.

The runs-on key specifies the type of machine the job will run on, such as 'ubuntu-latest'.

3fill in blank

hard

Fix the error in the step that runs a shell command.

Git

steps:
  - name: Run a command
    run: [1]

Drag options to blanks, or click blank then click option'

Aecho Hello World

Brun echo Hello World

Cecho 'Hello World'

Drun: echo Hello World

Attempts:

3 left

💡 Hint

Common Mistakes

Writing 'run echo Hello World' which repeats the keyword.

Using 'run: echo Hello World' inside the run value.

The run key expects the shell command directly, like 'echo Hello World'. Adding 'run' again or extra colons causes errors.

4fill in blank

hard

Fill both blanks to set up a step that checks out the repository code.

Git

steps:
  - name: Checkout code
    uses: [1]
    with:
      [2]: 'v3'

Drag options to blanks, or click blank then click option'

Aactions/checkout@v3

Bactions/checkout@v2

Cref

Dversion

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'actions/checkout@v2' when the latest is v3.

Using 'ref' instead of 'version' as the parameter name.

The uses key specifies the action to use, here 'actions/checkout@v3'. The with key can specify parameters like 'version' to choose the version tag.

5fill in blank

hard

Fill all three blanks to create a step that sets up Node.js version 16 and runs npm install.

Git

steps:
  - uses: actions/setup-node@[1]
    with:
      node-version: '[2]'
  - name: Install dependencies
    run: [3]

Drag options to blanks, or click blank then click option'

Av3

B16

Cnpm install

Dv2

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'v3' for setup-node which may not exist.

Using 'npm install' without quotes or with extra words.

The setup-node action version is often 'v2'. The Node.js version is set with 'node-version'. The command to install packages is 'npm install'.

Practice

1. What is the main purpose of GitHub Actions in a repository?

easy

A. To automate tasks like testing and deployment when events happen

B. To store large files in the repository

C. To manage user permissions on the repository

D. To create branches automatically

Solution

1. Step 1: Understand GitHub Actions role

   GitHub Actions automate workflows triggered by events such as code pushes or pull requests.

2. Step 2: Compare options with purpose

   Options B, C, and D describe other GitHub features, not automation tasks.

3. Final Answer:

   To automate tasks like testing and deployment when events happen -> Option A

4. Quick Check:

   Automation = A [OK]

Hint: GitHub Actions = automation triggered by events [OK]

Common Mistakes:

• Confusing GitHub Actions with file storage
• Thinking it manages user permissions
• Assuming it creates branches automatically

2. Which of the following is the correct location to place a GitHub Actions workflow file?

easy

A. .git/actions/

B. .github/workflows/

C. workflows/.github/

D. actions/workflows/

Solution

1. Step 1: Recall workflow file location

   GitHub Actions workflows must be stored in the .github/workflows/ directory in the repository.

2. Step 2: Verify other options

   Options B, C, and D do not match the required directory structure for workflows.

3. Final Answer:

   .github/workflows/ -> Option B

4. Quick Check:

   Workflow path = .github/workflows/ [OK]

Hint: Workflow YAML files go inside .github/workflows/ folder [OK]

Common Mistakes:

• Placing workflow files outside .github/workflows/
• Using incorrect folder names like .git or actions
• Confusing workflows folder location

3. Given this workflow snippet, what will happen when code is pushed to the main branch?

name: Test Workflow
on:
  push:
    branches:
      - main
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - run: echo "Build started"

medium

A. The workflow runs and prints 'Build started' on push to main

B. The workflow runs but does nothing on push to main

C. The workflow runs only on pull requests, not push

D. The workflow fails due to syntax error

Solution

1. Step 1: Analyze trigger event

   The workflow triggers on push events to the main branch as specified under 'on: push: branches: - main'.

2. Step 2: Check job steps

   The job named 'build' runs on ubuntu-latest and executes a step that runs the command echo "Build started".

3. Final Answer:

   The workflow runs and prints 'Build started' on push to main -> Option A

4. Quick Check:

   Push to main triggers echo output [OK]

Hint: Push to main triggers echo command in workflow [OK]

Common Mistakes:

• Thinking workflow triggers on pull requests only
• Assuming no output is printed
• Believing there is a syntax error

4. Identify the error in this workflow YAML:

name: CI
on: push
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - name: Run tests
        run: pytest
      - name: Deploy
        run: deploy.sh
        if: success()

medium

A. The 'if' condition syntax is incorrect; should be 'if: success()' without indentation

B. The 'steps' list is missing a dash before 'Deploy'

C. The 'if' condition is invalid; it should be 'if: ${{ success() }}'

D. The 'runs-on' key is misspelled

Solution

1. Step 1: Review 'if' condition syntax in GitHub Actions

   GitHub Actions requires expressions inside ${{ }} for conditions, so 'if: success()' is invalid syntax.

2. Step 2: Validate other parts

   'runs-on' is correctly spelled, and the steps list has proper dashes. Indentation is correct.

3. Final Answer:

   The 'if' condition is invalid; it should be 'if: ${{ success() }}' -> Option C

4. Quick Check:

   Conditions need ${{ }} syntax [OK]

Hint: Use ${{ }} for conditions in GitHub Actions [OK]

Common Mistakes:

• Omitting ${{ }} around conditions
• Misplacing dashes in steps list
• Misspelling 'runs-on'

5. You want a GitHub Actions workflow that runs tests only when code is pushed to the 'develop' branch or when a pull request targets 'develop'. Which 'on' configuration is correct?

hard

A. on:
push:
branches:
- develop
pull_request:
branches:
- main

B. on:
push:
branches:
- main
pull_request:
branches:
- develop

C. on:
push:
branches:
- main
pull_request:
branches:
- main

D. on:
push:
branches:
- develop
pull_request:
branches:
- develop

Solution

1. Step 1: Understand event triggers needed

   The workflow should trigger on push to 'develop' and on pull requests targeting 'develop'.

2. Step 2: Match branches in 'on' configuration

   on: push: branches: - develop pull_request: branches: - develop correctly specifies both push and pull_request events with branches set to 'develop'. Other options mix 'main' and 'develop' incorrectly.

3. Final Answer:

   on: push: branches: - develop pull_request: branches: - develop -> Option D

4. Quick Check:

   Push and PR on develop branch = C [OK]

Hint: Match branch names exactly in push and pull_request triggers [OK]

Common Mistakes:

• Mixing 'main' and 'develop' branches in triggers
• Omitting pull_request event
• Using incorrect indentation in YAML