2a Activity: Git and GitHub

Goal

We will create a brand-new practice repository on GitHub, open it in Codespaces, make one change, commit it, push it, and mark a shared version with a tag.

Note: The checkboxes on this page are only stored locally in your browser. They are not submitted or synced anywhere.

Progress: 0 / 0 steps complete.

Activity

1. Create A Repository

Start on GitHub in Chrome or Edge.

1. Go to https://github.com.
2. Click + in the upper-right corner.
3. Choose New repository.
4. Name the repository python_tmr_practice.
5. Choose Private.
6. Check Add a README file.
7. Click Create repository.

I created a new private GitHub repository with a README.

I confirmed this is a new practice repository, not my fork of the course repository.

2. Open it in Codespaces

From the new repository page:

1. Click the green Code button.
2. Click the Codespaces tab.
3. Click Create codespace on main.
4. Wait for VS Code Web to open.

If GitHub asks whether you trust the authors of the files, choose the “Yes” option.

I opened the new practice repository in Codespaces.

I opened Source Control in VS Code Web.

3. Make One Change

Open README.md.

Add a short research-project note, such as:

## Project Notes

This repository is a practice project for learning Git and GitHub.

Save the file.

Return to Source Control and click the changed file to review the diff.

I edited and saved README.md.

I reviewed the diff in Source Control.

Useful terminal reference:

git status --short
git diff

4. Commit the Change

In Source Control:

1. Find README.md under Changes.
2. Hover over README.md and click the + button to stage it.
3. Confirm that README.md moved from Changes to Staged Changes.
4. Write a descriptive commit message in the message box.
5. Click Commit.

If you have multiple changed files, stage only the files that belong together in this commit.

A good message for this practice change might be:

Added project notes to README.

I staged README.md.

I wrote a descriptive commit message.

I committed the change.

Useful terminal reference:

git add README.md
git commit -m "Added project notes to README."
git log --oneline --max-count=5

5. Push To GitHub

In VS Code Web, use Sync Changes or Push (from the … menu) in Source Control.

Then return to the repository page on GitHub and confirm the README change appears there.

I pushed or synced the commit to GitHub.

I found the updated README on GitHub.

Useful terminal reference:

git push

6. Mark A Shared Version

Now pretend this repository contains a draft you are sending to coauthors.

In Source Control:

1. Find the Graph section.
2. Right-click the most recent commit.
3. Choose Create Tag….
4. Name the tag 2026-06-03-to-MP, or substitute “MP” with the initials of your imaginary coauthor.
5. Confirm the tag.

Then push the tag to GitHub from the terminal:

git push origin 2026-06-03-to-MP

Return to the repository page on GitHub and confirm that the tag appears.

I created a tag from the Source Control graph.

I found the tag on GitHub.

I can explain why a tag is useful when sending a draft or submitting a paper.