Tinkercademy Bootcamp 2026 - Coding Labs

This repository was cloned from Stanford CS106L, a course on Standard C++ programming. All credit for the original starter code and assignment design goes to the CS106L course staff.

The assignments here have been modified from the original course materials.

Prerequisites

You need:

• g++ with C++20 support (gcc 10+, ideally 13+; or clang 15+).
  • macOS: brew install gcc, then make sure g++ resolves to the Homebrew version (e.g. g++-14), not Apple's clang alias.
  • Linux (Debian/Ubuntu): sudo apt-get install g++ (verify g++ --version is 10 or higher).
  • Windows: install the MinGW-w64 toolchain.
• git — install from https://git-scm.com/downloads if git --version doesn't work.
• An editor. VSCode with the C/C++ extension works well, but anything will do.

Getting Started

Clone this repository and cd into the assignment you're working on:

git clone git@github.com:tinkercademy-bootcamp/2026-coding-labs.git
cd 2026-coding-labs/assignment1

Each assignment has its own README.md with build and run instructions. To pull updates later:

git pull origin main

Syncing With the Template Repo

If you created your repo using GitHub's "Use this template" button, your copy has no shared history with this template, so git pull from your own origin won't bring in new assignments. To pull in updates from this template while keeping your own changes, add this repo as an upstream remote and merge from it.

One-time setup — add the template as upstream:

# check your current remotes (origin should be your own repo)
git remote -v

# add this template repo as upstream
git remote add upstream https://github.com/tinkercademy-bootcamp/2026-coding-labs.git

To sync (run this whenever new assignments are released):

# fetch the latest changes from the template
git fetch upstream

# merge them into your current branch
# --allow-unrelated-histories is required the first time, because
# "Use this template" creates a repo with no shared commit history
git merge upstream/main --allow-unrelated-histories

If there are merge conflicts (because you edited files the template also changed), open the conflicting files, fix the <<<<<<< / >>>>>>> markers, then:

git add .
git commit

Finally, push the synced result up to your own repo:

git push origin main

Quick reference:

• origin — your own copy of the repo
• upstream — the original template repo

Useful inspection commands before/after merging:

git status
git branch
git log --oneline --graph --all --decorate