Why Git integrates with CI/CD - See It in Action

Why Git Integrates with CI/CD

📖 Scenario: You work in a team that builds software. You use Git to save your code changes. Your team wants to make sure the code is always tested and ready to use. This is done using CI/CD tools that run tests and deploy code automatically.

🎯 Goal: Learn how Git connects with CI/CD by creating a simple Git repository, adding a configuration file to trigger CI/CD, and seeing the result of the integration.

📋 What You'll Learn

Create a Git repository with a README file

Add a CI/CD configuration file named .github/workflows/ci.yml

Write a simple CI job that runs on push

Show the Git commands to push changes and trigger CI/CD

💡 Why This Matters

🌍 Real World

Teams use Git with CI/CD to automatically test and deploy code changes, saving time and reducing errors.

💼 Career

Understanding Git and CI/CD integration is essential for software developers, DevOps engineers, and anyone working in modern software teams.

1

Create a Git repository with a README file

Initialize a Git repository in the current folder using git init. Then create a file named README.md with the exact content # My Project. Finally, add the file to Git using git add README.md.

Git

# Initialize Git repository and add README.md
# Your code here

Hint

Use git init to start a new repository. Use echo to create the README file. Use git add to stage the file.

2

Add a CI/CD configuration file

Create a folder named .github/workflows. Inside it, create a file named ci.yml with the following content exactly:

name: CI
on: [push]
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - run: echo "Running tests..."

Git

git init

echo "# My Project" > README.md

git add README.md
# Create .github/workflows/ci.yml with CI job
# Your code here

Hint

Create the folders with mkdir -p. Use echo with escaped quotes to write the YAML file.

3

Commit and push changes to trigger CI/CD

Commit your changes with the message "Add CI workflow" using git commit -m "Add CI workflow". Then push to the remote repository using git push origin main. Assume the remote is already set.

Git

git init

echo "# My Project" > README.md

git add README.md

mkdir -p .github/workflows

echo "name: CI
on: [push]
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - run: echo \"Running tests...\"" > .github/workflows/ci.yml
# Commit and push changes
# Your code here

Hint

Use git commit -m to save changes with a message. Use git push origin main to send changes to the remote.

4

Show the output of the CI job running

Print the exact text Running tests... to simulate the CI job output.

Git

git init

echo "# My Project" > README.md

git add README.md

mkdir -p .github/workflows

echo "name: CI
on: [push]
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - run: echo \"Running tests...\"" > .github/workflows/ci.yml

git add .github/workflows/ci.yml

git commit -m "Add CI workflow"

git push origin main

# Print the CI job output
# Your code here

Hint

Use echo "Running tests..." to show the CI job output.

Practice

1. Why is Git commonly integrated with CI/CD pipelines in software development?

easy

A. To replace the need for writing code documentation

B. To manually approve every code change before merging

C. To store large binary files efficiently

D. To automatically test and deploy code when changes are made

Solution

1. Step 1: Understand Git's role in code changes

   Git tracks code changes and allows developers to push updates to a shared repository.

2. Step 2: Connect Git with CI/CD automation

   Integrating Git with CI/CD triggers automated tests and deployments when code is pushed, speeding up delivery and catching errors early.

3. Final Answer:

   To automatically test and deploy code when changes are made -> Option D

4. Quick Check:

   Git + CI/CD = Auto test & deploy [OK]

Hint: Git triggers CI/CD to automate tests and deployment [OK]

Common Mistakes:

• Thinking Git replaces documentation
• Believing Git integration means manual approvals
• Confusing Git with file storage tools

2. Which Git event commonly triggers a CI/CD pipeline automatically?

easy

A. git clone

B. git push

C. git status

D. git branch

Solution

1. Step 1: Identify Git commands related to repository changes

   Commands like git push send local commits to the remote repository.

2. Step 2: Understand CI/CD triggers

   CI/CD pipelines usually start when new code is pushed to the repository, so git push triggers the pipeline.

3. Final Answer:

   git push -> Option B

4. Quick Check:

   Push triggers CI/CD [OK]

Hint: CI/CD pipelines start on git push events [OK]

Common Mistakes:

• Confusing git clone with triggering pipelines
• Thinking git status triggers CI/CD
• Assuming git branch triggers pipelines

3. Given this Git commit and CI/CD setup, what happens after running git push origin main?

1. Developer commits code locally
2. Runs git push origin main
3. CI/CD pipeline is configured to run tests on push to main branch

medium

A. The local commit is deleted

B. The code is deployed without any tests

C. The pipeline runs tests automatically on the new code

D. Nothing happens until manual approval

Solution

1. Step 1: Understand the push triggers pipeline

   Pushing code to the main branch triggers the CI/CD pipeline configured to run tests on that branch.

2. Step 2: Identify pipeline behavior

   The pipeline runs automated tests on the new code before deployment to catch errors early.

3. Final Answer:

   The pipeline runs tests automatically on the new code -> Option C

4. Quick Check:

   Push to main triggers tests [OK]

Hint: Push to main runs tests automatically [OK]

Common Mistakes:

• Assuming deployment happens without tests
• Thinking manual approval is always needed
• Believing local commits affect remote pipeline

4. A developer notices the CI/CD pipeline does not start after pushing code. Which Git-related issue could cause this?

medium

A. Pushing to a branch not monitored by the pipeline

B. Using git commit without git push

C. Running git status before pushing

D. Deleting the local repository

Solution

1. Step 1: Check branch monitored by CI/CD

   CI/CD pipelines usually watch specific branches like main or develop. Pushing to an unmonitored branch won't trigger the pipeline.

2. Step 2: Understand push vs commit

   While committing saves changes locally, only pushing sends changes to remote and triggers CI/CD. But here, the problem is the branch.

3. Final Answer:

   Pushing to a branch not monitored by the pipeline -> Option A

4. Quick Check:

   Branch must be monitored to trigger CI/CD [OK]

Hint: Pipeline triggers only on monitored branches [OK]

Common Mistakes:

• Confusing commit with push
• Thinking git status triggers pipeline
• Assuming deleting local repo affects remote pipeline

5. How does integrating Git with CI/CD pipelines improve software delivery in a team environment?

hard

A. By automatically running tests and deployments on code changes, reducing errors and speeding releases

B. By requiring developers to manually test and deploy every change

C. By storing all code versions in a single large file

D. By preventing any code changes without manager approval

Solution

1. Step 1: Understand automation benefits

   Git integration with CI/CD automates testing and deployment, catching errors early and reducing manual work.

2. Step 2: Recognize impact on team delivery

   This automation helps teams release software faster and with higher quality by ensuring code is tested before deployment.

3. Final Answer:

   By automatically running tests and deployments on code changes, reducing errors and speeding releases -> Option A

4. Quick Check:

   Automation improves delivery speed and quality [OK]

Hint: Automation with Git + CI/CD speeds delivery and reduces errors [OK]

Common Mistakes:

• Thinking manual testing is required every time
• Confusing Git with file storage
• Assuming all changes need manager approval