Writing good commit messages in Git - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to create a new commit with a message.

Git

git commit -m "[1]"

Drag options to blanks, or click blank then click option'

Agit push origin main

BFix typo in README

Cgit status

Dgit add .

Attempts:

3 left

💡 Hint

Common Mistakes

Using commands like 'git push' or 'git add' instead of a message.

Leaving the message empty or unclear.

The -m option lets you add a commit message directly. A good message briefly explains the change, like "Fix typo in README".

2fill in blank

medium

Complete the command to add all changed files before committing.

Git

git [1] .

Drag options to blanks, or click blank then click option'

Acommit

Bstatus

Cpush

Dadd

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'git commit' before staging files.

Using 'git push' instead of staging.

The git add . command stages all changed files in the current folder for the next commit.

3fill in blank

hard

Fix the error in the commit message command by filling the blank.

Git

git commit -m [1]

Drag options to blanks, or click blank then click option'

A"Fix bug in login"

BFix bug in login

CFix bug in login"

D'Fix bug in login

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting to add quotes around the message.

Using mismatched or missing quotes.

The commit message must be inside quotes. Without quotes, the shell treats words as separate commands, causing errors.

4fill in blank

hard

Fill both blanks to write a commit message that starts with a capital letter and is under 50 characters.

Git

git commit -m "[1] [2]"

Drag options to blanks, or click blank then click option'

AFix

Btypo

Cin

DREADME

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase start words.

Writing too long messages in the first line.

A good commit message starts with a capital verb and is short. "Fix typo" is clear and concise.

5fill in blank

hard

Fill all three blanks to write a commit message with a capital verb, a short description, and a reference to an issue number.

Git

git commit -m "[1] [2] #[3]"

Drag options to blanks, or click blank then click option'

AAdd

Blogin

C42

Dbug

Attempts:

3 left

💡 Hint

Common Mistakes

Not capitalizing the first word.

Leaving out the issue number reference.

Writing vague descriptions.

This message starts with a capital verb 'Add', describes the change 'login', and references issue number 42 with '#42'.