Deployment triggers from tags in Git - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to list all tags in the repository.

Git

git [1]

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

Atag

Bbranch

Ccommit

Dcheckout

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'git branch' lists branches, not tags.

Using 'git commit' shows commits, not tags.

The git tag command lists all tags in the repository.

2fill in blank

medium

Complete the command to create a new tag named 'v1.0'.

Git

git [1] v1.0

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

Apush

Bcheckout

Ccommit

Dtag

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'git push' sends data to remote but does not create tags.

Using 'git checkout' switches branches, not tags.

The git tag v1.0 command creates a new tag named 'v1.0'.

3fill in blank

hard

Fix the error in the command to push tags to the remote repository.

Git

git push origin [1]

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

A--tags

Bbranch

Ccommit

DHEAD

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'branch' or 'HEAD' pushes branches, not tags.

Using 'commit' is invalid in this context.

The --tags option pushes all tags to the remote repository.

4fill in blank

hard

Fill in the blank to complete the GitHub Actions trigger for tags starting with 'v'.

Git

on:
  push:
    tags:
      - '[1]*'

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

Atag-

Brelease-

Cv

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'release-' or 'tag-' prefixes do not match version tags starting with 'v'.

The trigger pattern 'v*' matches tags starting with 'v', commonly used for version tags.

5fill in blank

hard

Fill both blanks to complete the GitHub Actions job that runs only on tag pushes starting with 'v'.

Git

jobs:
  deploy:
    if: startsWith(github.ref, 'refs/tags/[1][2]')
    runs-on: ubuntu-latest
    steps:
      - name: Deploy
        run: echo "Deploying version tag"

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

Av

B-

C*

Drelease

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'release' instead of 'v-' causes the condition to fail.

The condition checks if the tag starts with 'v-' followed by any characters, matching version tags like 'v-1.0'.

Practice

1. What is the main purpose of using tags in Git for deployment triggers?

easy

A. To merge multiple branches into one

B. To delete old branches automatically

C. To create new branches for development

D. To mark specific versions of code for deployment

Solution

1. Step 1: Understand what tags represent in Git

   Tags are labels that mark specific points in Git history, usually used for releases or versions.

2. Step 2: Connect tags to deployment triggers

   Deployment systems listen for tag pushes to know when to deploy a specific version of the code.

3. Final Answer:

   To mark specific versions of code for deployment -> Option D

4. Quick Check:

   Tags mark versions = C [OK]

Hint: Tags label versions for deployment triggers [OK]

Common Mistakes:

• Confusing tags with branches
• Thinking tags delete branches
• Assuming tags create new branches

2. Which Git command correctly creates a tag named v1.0 and pushes it to the remote repository?

easy

A. git create tag v1.0 && git push tags

B. git push tag v1.0

C. git tag v1.0 && git push origin v1.0

D. git tag create v1.0 && git push origin tags

Solution

1. Step 1: Identify the correct command to create a tag

   The command git tag v1.0 creates a tag named v1.0 locally.

2. Step 2: Identify how to push the tag to remote

   git push origin v1.0 pushes the specific tag to the remote repository.

3. Final Answer:

   git tag v1.0 && git push origin v1.0 -> Option C

4. Quick Check:

   Create tag + push tag = A [OK]

Hint: Use 'git tag' then 'git push origin tagname' [OK]

Common Mistakes:

• Using 'git push tag' which is invalid
• Trying 'git create tag' which is not a Git command
• Pushing 'tags' instead of specific tag name

3. Given this GitHub Actions snippet, what triggers the deployment workflow?

on:
  push:
    tags:
      - 'release-*'

medium

A. Any push of tags starting with 'release-'

B. Any push to branches named 'release-*'

C. Any push to any branch

D. Any push of tags named exactly 'release-*'

Solution

1. Step 1: Understand the trigger syntax

   The on.push.tags with pattern 'release-*' listens for tag pushes starting with 'release-'.

2. Step 2: Differentiate tags from branches

   This does not trigger on branches, only on tags matching the pattern.

3. Final Answer:

   Any push of tags starting with 'release-' -> Option A

4. Quick Check:

   Push tags matching pattern = A [OK]

Hint: Tags trigger with 'push.tags' and pattern [OK]

Common Mistakes:

• Confusing tags with branches in triggers
• Thinking exact tag name match is required
• Assuming all pushes trigger workflow

4. You set this in your GitHub Actions workflow:

on:
  push:
    tags:
      - 'v*'

But pushing tag release1 does NOT trigger the workflow. Why?

medium

A. The tag name does not match the pattern 'v*'

B. Tags cannot trigger workflows in GitHub Actions

C. The workflow file is missing from the repository

D. The push event only triggers on branches, not tags

Solution

1. Step 1: Analyze the tag pattern

   The pattern 'v*' matches tags starting exactly with 'v', like 'v1.0', but 'release1' starts with 'release', so it does not match.

2. Step 2: Confirm tag triggers work

   GitHub Actions supports tag push triggers, so the problem is pattern mismatch.

3. Final Answer:

   The tag name does not match the pattern 'v*' -> Option A

4. Quick Check:

   Pattern mismatch blocks trigger = B [OK]

Hint: Check tag name matches trigger pattern exactly [OK]

Common Mistakes:

• Assuming any tag triggers workflow
• Thinking tags can't trigger workflows
• Ignoring pattern matching rules

5. You want to deploy only when a tag matching deploy-* is pushed. Which GitHub Actions trigger configuration is correct?

hard

A. on:
push:
tags:
- 'release-*'

B. on:
push:
tags:
- 'deploy-*'

C. on:
tag_push:
pattern: 'deploy-*'

D. on:
push:
branches:
- 'deploy-*'

Solution

1. Step 1: Identify correct event for tag push

   The push event with tags key listens for tag pushes matching patterns.

2. Step 2: Match the pattern to desired tags

   The pattern 'deploy-*' matches tags starting with 'deploy-', exactly what is needed.

3. Step 3: Eliminate incorrect options

   on: push: branches: - 'deploy-*' listens to branches, not tags. on: tag_push: pattern: 'deploy-*' uses invalid syntax. on: push: tags: - 'release-*' matches wrong tag pattern.

4. Final Answer:

   on: push: tags: - 'deploy-*' -> Option B

5. Quick Check:

   Push tags with correct pattern = D [OK]

Hint: Use 'push.tags' with correct pattern for deployment triggers [OK]

Common Mistakes:

• Using branches instead of tags for deployment triggers
• Using invalid event names like 'tag_push'
• Mismatching tag patterns