# git exercise. Single developer and local repository.

# First move to a safe place:

# Run the 'git' command and read the output, its a useful summary.

# Ask git what it knows about the status of the current directory.

# Introduce yourself to git (set the variables for name and email):

# Verify that git has correctly stored your config (see 'git help config')

# Create a directory for this exercise and enter it.

# Create a new git repository within the current directory.

# Verify that you have a brand new ".git/" directory...
# ...and its content.

# Check the status and compare the output to the one from last time

# Create a file named hello.py that prints some salutation.

# Check the status and compare the output to the one from last time

# Put hello.py in the staging area
# and check how the status changes

# Now record commit to the repository.

# Check status again, it is instructive.

# Edit hello.py some more.

# See how the status changes accordingly.

# Show the changes between current and staged files.

# Add changes into the staging area (index)...
# and see how the status changes accordingly.

# Edit hello.py again, e.g., adding another print statement.

# And again the status..
# and the changes between the 3 different versions.

# Commit *only* changes from the staging area.

# Verify that changes not added to the staging area were not recorded.

# Commit all changes in hello.py skipping the staging area.

# Edit hello.py again and create a new file.

# Inspect the status and the changes.

# Commit everything, skipping the staging area where possible.

# Check that you really commited everything.

# See the logs of all commits.

# See the logs of all commits with the git GUI.

# Go crazy and mess with your files. Remove files.

# Oh no! What have you done! Shame! Verify status and changes.

# Get rid of the last untracked changes

# Verify that everything is back to normal.

#Relax: your work is safe.