GitHub getting started

What you are setting up

Your course repository exists in two connected places.

• The folder on your computer is where you create and edit files.
• The private copy on GitHub is what the instructor can access after you push.

Saving a file changes the local folder. A commit records a meaningful version of those changes. A push sends the commits to GitHub. Work is not submitted until the pushed files are visible on github.com.

1 · Prepare your account and GitHub Desktop

1. Go to github.com and sign in or create an account.
2. Verify the email address connected to the account.
3. Record your username somewhere you can retrieve it.
4. Download and install GitHub Desktop.
5. Sign in to GitHub Desktop with the same GitHub account.

Use an account you expect to retain after the course. Never place your GitHub password or recovery codes in a course file.

The remaining sections are completed during Session 1.

2 · Create the private course repository

1. On GitHub, select New repository.
2. Name it ba3tad-26-surname, replacing surname with your surname.
3. Set visibility to Private.
4. Select Add a README file.
5. Create the repository.

Check the repository page before continuing. The name should be correct and a README.md should be visible. The Private label should appear near the title.

3 · Give the instructor access

1. In the repository, open Settings.
2. Open Collaborators or Collaborators and teams under access settings.
3. Select Add people.
4. Add the GitHub user scdenney.

The repository remains private. Collaborator access allows the instructor to see the files you submit.

4 · Connect the repository to GitHub Desktop

1. Confirm that GitHub Desktop is signed into the same GitHub account.
2. Choose Clone a repository from the Internet.
3. Select ba3tad-26-surname.
4. Choose a memorable location on your computer, such as a course folder inside Documents.
5. Select Clone.

Do not create a second folder with the same name inside the cloned repository. In GitHub Desktop, use Repository → Show in Finder on macOS or Show in Explorer on Windows whenever you are unsure which folder is connected.

5 · Make and push a test change

1. Open the cloned README.md in a plain-text editor. Use TextEdit in plain-text mode on macOS, Notepad on Windows, or any code editor.
2. Add your full name and the line BA3 Text as Data · AY 2026–2027.
3. Save the file.
4. Return to GitHub Desktop and confirm that README.md appears under Changes.
5. Enter the summary Complete initial repository setup.
6. Select Commit to main.
7. Select Push origin.
8. Open the repository on github.com and confirm that the new text appears.

If the text is visible online, the local, commit, and push workflow works.

The workflow you will repeat

1. Put work in the correct local demo folder.
2. Review the changed files in GitHub Desktop.
3. Write a specific commit summary.
4. Commit to main.
5. Push to GitHub.
6. Verify the required files on github.com.

You do not need branches or pull requests for the normal individual course workflow.

If something goes wrong

• If no changes appear, use Show in Finder/Explorer and confirm that you edited the cloned folder.
• If no Push origin button appears, confirm that you committed the change.
• If the repository is missing from GitHub Desktop, confirm that Desktop is signed into the correct account. Then use File → Clone repository.
• If the instructor cannot open the link, confirm that the collaborator invitation was sent to scdenney and accepted.
• If you see a conflict or unfamiliar warning, stop and record the exact message. Do not delete the repository or create replacement copies.

Optional background

The Resources page includes GitHub’s Hello World guide if you want a broader explanation of repositories, branches, commits, and pull requests. Those extra concepts are useful background but are not required for the initial setup above.