Skip to main content

GitHub Setup Guide

GitHub Setup Guide

guide · github

Free

GitHub Setup Guide

This browser will not display the PDF inline. Open the PDF.

Learn the branch-to-review workflow with a safe practice repository.

BEGINNER / VERSION CONTROL

1. Set the stage

GitHub supports your AI workflow; it is not a model. Start in the browser so you can learn repositories, branches, and pull requests first.

1. Create a practice repository

Sign in at github.com. Create a private learning repository with a README. Keep real credentials and client files out.

2. Create a working branch

Create a branch named practice/readme. Edit the README with a short description of what you plan to build.

3. Commit & request review

Commit the change with a clear message. Open a pull request and inspect the file diff before merging your practice change.

4. Add local tools later

Install GitHub Desktop for a visual local workflow, or Git plus an editor. Clone the practice repository and confirm the correct branch.

2. Lean working stack

| Stage | Role | | --- | --- | | Editor | Make a change | | GitHub | Review the diff | | Checks | Validate behavior | | Preview | Inspect the result |

Arrows in the visual sheet show the order of work. External connections require separate setup. Optional tools may be replaced with ones you already use. This is a suggested stack for this task, not a universal optimum.

Use checkpoints deliberately

Keep commits small and descriptive. A branch is a place to work; a pull request is a place to review the proposed change.

Keep the first stack lean

Browser-only is enough for this exercise. Add GitHub Desktop or Git when you need local files, and CI when checks are ready.

3. First practice task

Create a README with the project goal, who it helps, and three acceptance checks. Commit on a practice branch, open a pull request, review the diff, and merge only that practice change.

Your setup is working when

Your pull request shows the expected change, the reviewed commit is on the main branch, and no secret or unrelated file appears in the diff.

Troubleshooting

Cannot push? Check access and sign-in. Wrong files? Inspect the branch and diff. Blocked merge? Resolve the check or permission requirement.

Series 05 / 40

Back to Quill UniversityDownload MDDownload PDFDownload PNG