* Instead of creating a merge commit, Git simply moves the target branch pointer forward to point to the latest commit of the feature branch. * You can prevent this by running `git merge --no-ff `, which forces Git to create a merge commit, preserving the visual branch boundary in the history log.

# How it works:

💬Answer

Instead of creating a merge commit, Git simply moves the target branch pointer forward to point to the latest commit of the feature branch.
You can prevent this by running git merge --no-ff <branch>, which forces Git to create a merge commit, preserving the visual branch boundary in the history log.

Related Git & GitHub Questions

View All Git & GitHubQuestions →

What is Git, and how does its distributed model differ from older centralized version control systems?

# Why it is Used:

What is version control, and why is it considered the absolute starting point for any DevOps pipeline?

Can you explain the main architectural areas of Git? How do files transition between them?

Created by

Apurv Gujjar

DevOps & Cloud Engineer

Specialized in:DevOpsAWSGCPKubernetesTerraformDocker

View Portfolio