GIT · Foundations · 10 min

Commit only the intended staged file

Both files are staged, but only one belongs in the release.

Not completed

Your task

Unstage scratch.txt without deleting it, then commit release.txt. Keep scratch.txt untracked.

What you’re aiming for

  • The new commit contains release.txt, not scratch.txt.
  • scratch.txt is still on disk with its original text.

1. Prepare your practice folder

Use Git 2.28 or newer. The setup commands below use a Bash-compatible shell: Git Bash on Windows, or Bash on Linux/macOS.

Create a new, empty folder for this exercise. If that name already exists, choose another new name. Continue only after you’re inside the new folder.

NEW PRACTICE FOLDER
mkdir opsrung-git-commit-staged-selection && cd opsrung-git-commit-staged-selection

Run these setup commands in that folder:

SETUP — RUN ONCE
git init --initial-branch=main
git config --local user.name 'Practice Learner'
git config --local user.email 'practice@example.invalid'
printf '%s\n' 'A disposable OpsRung practice repository.' > README.txt
git add -- README.txt
git commit -m 'Start practice'
printf '%s\n' 'Ship this.' > release.txt
printf '%s\n' 'Keep this locally.' > scratch.txt
git add release.txt scratch.txt
Only if your personal Git settings interfere

You can normally skip this. If a commit asks for a signing key, runs a custom hook, or changes line endings unexpectedly, these repository-local overrides keep this disposable exercise independent of those settings.

OPTIONAL REPOSITORY OVERRIDES
git config --local commit.gpgsign false
git config --local core.autocrlf false
git config --local core.hooksPath .git/practice-no-hooks

Retry the failed command afterward. These settings apply only inside this practice repository.

2. Try the task

Work toward the goal above. Start by inspecting the files or resources, then use a hint if you need one.

Hint 1

The index is the next snapshot, not the same thing as your working files.

Hint 2

git restore --staged removes a file from that snapshot.

Hint 3

Unstage scratch.txt before committing.

3. Review your result

Use these commands to look at your result and compare it with the goals. The website does not run or verify them.

REVIEW IN YOUR TERMINAL
git status
git log --oneline --graph --all -12

What you should see

  • The new commit contains release.txt, not scratch.txt.
  • scratch.txt is still on disk with its original text.

If your result differs: Work only in this exercise’s repository. Compare the branch, files, and history with every goal before marking complete.

Compare with one possible solution
ONE POSSIBLE SOLUTION — BASH
git restore --staged -- scratch.txt
git commit -m 'Record release only'

Other approaches are fine if you reach the same goal. Opening this solution does not mark the exercise complete.

Finished this exercise?

You decide when you’re done. Your choice is saved in this browser, and you can change it later.