APURV
  • Home
  • Journey
  • Projects
  • Blogs
  • Interview
  • Exams
Resume
APURV

Building scalable, secure, and production-ready cloud infrastructure. Automation first.

NAVIGATION

HomeExperienceProjectsCertificationsSkills

TECH STACK

AWSGCPK8sCI/CDLinuxDocker

CONNECT

LinkedInGitHubEmailResume

© 2026 Apurv Gujjar. All rights reserved.
Apurv Gujjar
Apurv GujjarDevOps & Cloud Engineer
|Interview Documentation
Portfolio
Handbooks
🎯Linux🐙Git & GitHub🤖GitHub Actions🌐Networking☁AWS🛠Terraform🐳Docker☸Kubernetes📊Monitoring🛡DevSecOps💰Cost Optimization🚨Incident Scenarios👤HR & Behavioral☁GCP🐍Python
Interview DocumentationGit & GitHubWalk me through your step-by-step process for resolving a merge conflict.
Back to all Git & GitHub questions
Q2

Walk me through your step-by-step process for resolving a merge conflict.

💬Answer

Resolving merge conflicts involves a structured process:

  1. Identify Conflicted Files: Git lists conflicted files. Run git status to view files marked both modified.
  2. Open Files & Inspect Conflict Markers: Locate the standard Git conflict markers in the source file:
    <<<<<<< HEAD
    Changes on the current active branch (e.g., main)
    =======
    Changes from the branch being merged in (e.g., feature)
    
  3. Edit Content: Manually edit the files to combine or select the desired changes, and remove all conflict markers.
  4. Stage Files: Stage the resolved files: git add <file-name>.
  5. Commit Resolution: Complete the merge operation: git commit -m "merge and resolve conflicts".

Related Git & GitHub Questions

View All Git & GitHubQuestions →
Q1

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

Q2

# Why it is Used:

Q3

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

Q4

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

Apurv Gujjar - DevOps & Cloud Engineer
Created by

Apurv Gujjar

DevOps & Cloud Engineer

Specialized in:DevOpsAWSGCPKubernetesTerraformDocker
View Portfolio