Video: Ignore files and clean untracked work safely
The video plays in YouTube’s player, in privacy-enhanced mode.
- 6 min video
- English narration · English and Arabic captions
- Watch on YouTube
Commit the course ignore policy, then preview and remove only a disposable untracked scratch file. Keep ignored build output, tracked work and recovery scope separate.
Read the full lesson
The article has every step and command from the video, the practice exercise and the questions.
Video transcript
The narration of the video, cue by cue.
- Start from the exact checkpoint.
- Name the branch, index and working version.
- Prepare only the isolated course copy.
- Save the exact shared ignore policy.
- Commit only the ignore file.
- Keep the scratch file deliberately untracked.
- Preview the exact named path first.
- Read every removal candidate.
- Do not widen the clean options.
- Remove only the disposable file.
- Verify what stayed as well as what disappeared.
- Does ignore erase tracked history?
- Rules hide untracked candidates; they do not rewrite history.
- What remains after scoped clean?
- Only the named untracked scratch is removed with these options.
- Does cleaning make a new commit?
- The operation removes disk bytes outside the index.
- Change input to include ignored files: scope?
- Expanded options change candidates; preview again before acting.
- Native clean ran. Is app Undo guaranteed?
- Native clean creates no GitTree journal or untracked-content backup.
- What proves the intended clean?
- Check both removed and preserved state with the named queries.
- Verify the actual result, not just a message.
- Predict the changed input before acting.
- Preserve useful work before recovery.
- Prove the checkpoint before continuing.
- Keep the verified result for the next step.