Good commit message

Learn what makes a good commit message.

Characteristics of a Good Commit Message

A good commit message should be concise, clear, and descriptive of the change. It should make it easy to understand what the change does or why it was made.

Add search filter

Imperative and Conventional Commits

With the imperative style, a message describes an action, such as Update the menu. Conventional Commits uses types such as feat: and fix: to identify the nature of a change.

feat: add search field
fix: correct login error

Exercise Create Conventional Commit Messages

Create two Conventional Commit messages for a new feature and a bug fix. Store them in featureMessage and fixMessage, then print them on separate lines.

Show example solution

let featureMessage = 'feat: profil sayfası ekle';
let fixMessage = 'fix: bağlantı hatasını düzelt';

console.log(featureMessage);
console.log(fixMessage);

Test yourself

Which of the following is a better commit message?
- Update
- Files changed
- Add validation to login form
- Did some stuff
Show answer

Add validation to login form — A good message clearly states the change. Generic phrases do not explain its purpose.

Complete the Conventional Commits Type

Yeni bir özellik ekleyen commit mesajı ____ ile başlayabilir.

Show answer

Yeni bir özellik ekleyen commit mesajı feat: ile başlayabilir.

Match Commit Message Principles

imperative

Action-oriented wording
concise

Remove unnecessary words
feat:

New feature type
fix:

Bug fix type

Next lesson: Summary - Commit

We Are Enhancing Your Experience

Cookie Preferences

Strictly Necessary Cookies

Analytical Cookies