Git Basics - Quiz

Initialize version control in the current project directory so Git starts tracking files.

Download an existing remote repository so you can work on it locally.

Stage all modified and new files in the current directory for the next commit.

Record staged changes with a descriptive message explaining the reasoning behind them.

See which files are modified, staged, or untracked before committing.

What is the main purpose of the staging area in Git?

After running git init in an existing project directory, what is the most important thing you should typically do next?

Which statement about git clone is accurate?

Which commit message subject best follows recommended conventions?

What does a pattern like node_modules/ in .gitignore do?

Order the steps to start tracking an existing project with Git and create the first commit.

Drag and drop to reorder, or use the arrows.

Order the steps to clone a remote repo, modify a file, and save the change.

Drag and drop to reorder, or use the arrows.

Order the steps to safely prepare a focused bugfix commit using the staging area.

Drag and drop to reorder, or use the arrows.

Order the steps to add a new ignore rule for build artifacts in an existing repository.

Drag and drop to reorder, or use the arrows.

You are on branch feature-login. What is the output of this command?

1git branch --show-current

You have staged changes. What will this command print?

1git status --short

After creating a commit with message "Add API client", what does this show?

1git log -1 --pretty=%s

Find the incorrect command in this workflow to save staged changes with a message.

Click on the line(s) that contain the bug.

git status

git add app.js

git commit "Implement caching layer"

git status

Identify the mistake in this attempt to create a repository and clone a remote.

Click on the line(s) that contain the bug.

mkdir project-name

cd project-name

git init https://example.com/repo.git

git status

Find the incorrect command in this workflow to ignore log files before committing.

Click on the line(s) that contain the bug.

echo "*.log" >> .gitignore

git add .

git commit -m "Ignore log files"

echo "debug.log" > debug.log

git add debug.log

git commit -m "Add debug log"

Match each Git concept to its description.

Click an item on the left, then click its match on the right. Click a matched item to unmatch.

Match each Git command to what it mainly helps you inspect.

Click an item on the left, then click its match on the right. Click a matched item to unmatch.

Match .gitignore patterns to what they ignore.

Click an item on the left, then click its match on the right. Click a matched item to unmatch.

Complete the commands to clone a repo into api-service and check its status.

Complete the commands to stage app.js and then commit it with a message.

Complete the commands to create a .gitignore and verify ignored files.

Click the line that shows which files are staged for commit.

Click on the line to select.

On branch main

Changes to be committed:

  (use "git restore --staged <file>..." to unstage)

        modified:   src/app.js

Changes not staged for commit:

        modified:   README.md

Click the line that indicates the current branch name.

Click on the line to select.

On branch feature-api

Changes not staged for commit:

  (use "git add <file>..." to update what will be committed)

        modified:   api/client.js

Untracked files:

        api/new-endpoint.txt

Click the line that shows an untracked file.

Click on the line to select.

On branch main

Your branch is up to date with 'origin/main'.

Untracked files:

  (use "git add <file>..." to include in what will be committed)

        scripts/deploy.sh