Git and GitHub Workflow

Git and GitHub Workflow

Git tracks changes in your project files. GitHub stores the remote copy of your personal repository.

Create the Repository Only Once

Create your personal it140-projects repository in Module Five.

Use that same repository for:

• Project One
• Module Six Milestone
• Project Two

Do not create a separate it140-projects repository for each module.

Save Work in Small Checkpoints

A basic checkpoint is:

git status
git add <files-you-changed>
git commit -m "Describe the work you completed"
git push

The top-level README provides activity-specific git add examples.

What git status Tells You

Use git status before committing.

It helps you see:

• Files you changed
• Files staged for the next commit
• Untracked files
• Whether your branch is ahead of or behind the remote

Read the output before running more Git commands.

Continue on Another Computer

If your personal repository already exists but is not on the computer you are using, clone your existing personal repository instead of creating another copy from the course template.

cd ~/Repos
gh repo clone "$(gh api user --jq .login)/it140-projects"
cd it140-projects
git status

If you already have the repository on both computers, push current work from one computer before pulling or continuing on the other.

Keep the Repository Private

Your personal project repository contains graded work. Keep it private unless current course policy or your instructor explicitly directs otherwise.

Do not post completed solutions in public Issues or Discussions.

GitHub Is Not the Submission System

A successful git push backs up your work to GitHub. It does not submit the activity for grading.

Use D2L Brightspace for each activity's required submission.