Intermediate LevelGit & GitHub

What is the Conventional Commits specification?

❓ Interview Prompt: Explain Conventional Commits syntax (feat, fix, chore, docs, BREAKING CHANGE), semantic versioning, and automated CHANGELOG generation.

Conventional Commits standardizes commit message syntax (e.g. feat(auth): add JWT login), enabling automated tools (semantic-release) to bump Semantic Versions and generate CHANGELOG.md files.

Code Implementation Example

bash

git commit -m "feat(auth): add OAuth2 Google login provider"
git commit -m "feat(api)!: drop legacy v1 REST endpoints

BREAKING CHANGE: v1 API endpoints removed."

💡Writing Conventional Commits with scope and breaking change footers.

🎯 Interview Key Takeaway

Follow Conventional Commits (feat, fix, BREAKING CHANGE) to automate semantic versioning and changelog generation.

#Conventional Commits#SemVer#Commit Standards#Intermediate

Back to all Git & GitHub Questions→

More Git & GitHub Interview Questions

Beginner LevelGit & GitHub

Compare git rebase versus git merge and explain how git bisect finds regressions.

Beginner LevelGit & GitHub

What is the difference between git init and git clone?

Beginner LevelGit & GitHub

What is the Conventional Commits specification?

Code Implementation Example

More Git & GitHub Interview Questions

Compare git rebase versus git merge and explain how git bisect finds regressions.

What is the difference between git init and git clone?

What are the Three Trees in Git (Working Directory, Staging Area / Index, Commit History)?