GIT · Foundations · 10 min
Untrack a file without deleting it
An ignore rule was added after a log had already been committed.
Not completedYour task
Remove runtime.log from Git tracking and commit that change. Keep the file and its contents on your computer.
What you’re aiming for
- runtime.log is ignored and no longer tracked.
- The file still contains the original sample log.
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.
mkdir opsrung-git-stop-tracking-log && cd opsrung-git-stop-tracking-log
Run these setup commands in that folder:
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' 'INFO synthetic event' > runtime.log git add -- runtime.log git commit -m 'Accidentally track log' printf '%s\n' '*.log' > .gitignore git add -- .gitignore git commit -m 'Ignore future logs'
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.
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
Ignore rules do not remove files already in the index.
Hint 2
The --cached option affects the index instead of deleting your working file.
Hint 3
Use git rm --cached -- runtime.log and commit.
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.
git status git log --oneline --graph --all -12
What you should see
- runtime.log is ignored and no longer tracked.
- The file still contains the original sample log.
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
git rm --cached -- runtime.log git commit -m 'Stop tracking generated log'
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.