How can I explore Git commands safely in a disposable local repository?

Create a new, clearly named directory just for practice, then enter it before running Git commands. For example, in a Bash-like terminal:

mkdir git-practice
cd git-practice
git init

Git documents git init as creating an empty repository, usually by making a .git directory in the working directory [S1]. This exercise starts locally in your practice directory and doesn’t require a hosted service.

Before each exercise, check that you are in the practice directory and run git status to see the repository state. If you are unsure where the terminal is, stop and check rather than running commands in a different folder. Keep the exercise to sample files in this directory; don’t copy in real project files or connect a remote.

Create a harmless sample file, then inspect the repository:

printf 'first note\n' > note.txt
git status
git diff
git add note.txt
git status

The Git tutorial demonstrates git status and git diff for inspecting repository state and changes, and git add for placing file contents in the index, also called the staging area [S2]. Compare the status before and after git add to observe the effect of staging the sample file.

Next, edit note.txt, for example by appending a line with printf 'second note\n' >> note.txt. Run git status and git diff again to inspect the result. Keep the filename and contents simple, and stage only the sample file you intend to practice with.

Before committing, run git status and decide whether you intend to record the staged changes. Git’s tutorial explains that a commit records the index in repository history; git add puts file contents into that index [S2]. So, review what you have staged before recording it.

For a small example, run:

git add note.txt
git status
git commit -m "Add practice note"
git status
git log

The tutorial covers adding, committing, and inspecting history with git log [S2]. After the commit, use git status and git log to inspect the repository state and history. If Git reports that it lacks a name or email identity, don’t use someone else’s details; stop and consult Git’s documentation about configuring an identity for this local practice repository.

Use a small loop: make one sample change, inspect the repository with git status and git diff, stage the change with git add, check the status again, and commit if you want to practice recording history. Then inspect the state and history with git status and git log. This follows the local workflow of staging, committing, and checking changes and history described in the Git tutorial [S2].

Keep each exercise confined to the disposable directory and use sample material only. Avoid commands whose effects you don’t understand, particularly ones that could remove files or alter history. Don’t add a remote or use hosted-service operations for this practice plan. The cited documentation supports the basic workflow here, not a guarantee that every Git command or shell operation is harmless. If a command’s effect is unclear, look up its documentation before running it.