Challenge 1: Check Git Configuration Settings

To begin, check your github configuration. Type the following in bash:

$ git config user.name

$ git config user.email

The output of the above commands should return your username and email for git. If it does not or it returns nothing, you will need to review the instructions for configuring git locally on your computer.

Challenge 2: Make Changes to Files

STEP 1: Make Changes to a File

• Use Shell to navigate to your forked repository (the practice-git-skillz directory).

If you don’t have this repo locally - you can clone it using the following url: https://github.com/your-user-name-here/practice-git-skillz

• Launch Jupyter Notebook inside that directory. (If you are working on a JupyterHub you can skip this step!)

• Open the Jupyter Notebook file in that directory(homework-example.ipynb) and make some changes to the file as follows:

  • Add a markdown cell to the notebook
  • In the cell add a heading and then some text below.

STEP 2: Check the Status of Your Changed File

Return to your shell tool. Run the command:

git status

to check the status of current changes. It should show that there is a change to the file.

$ git status
On branch main
Your branch is up-to-date with 'origin/main'.
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   homework-example.ipynb
    
no changes added to commit (use "git add" and/or "git commit -a")

The output from git status indicates that you have modified the file homework-example.ipynb. To add these changes to your git history you need to:

1. add the changes, and then
2. commit the changes using a useful message that describes what you changed.

STEP 3: Add and Commit Changed Files

You will use the add and commit functions to add and commit your changed files.

• git add: takes a modified file in your working directory and places the modified version in a staging area.

• git commit: takes everything from the staging area and makes a permanent snapshot of the current state of your repository that is associated with a unique identifier.

These two commands make up the bulk of many workflows that use git for version control.

STEP 4: Push Your Changes to GitHub.com

Once you have added and commited your changes, you are ready to push them to GitHub.com. Use:

$ git push

to push the changes to your fork.

Challenge 3

• Rename the Jupyter Notebook in your repository. Then add and commit the file. Push the renamed file up to Github. Then check that it’s there by going to github.com!

• Add a new file to the repo, commit the change and push it to github.com. Check to see that it’s there.
• Use git log to view the history of changes that you’ve made.