The workshop is two hours of hands-on work, so there is no time to install software during it. Do this beforehand. It takes about 20 minutes, and at the end there is a checklist to confirm you are ready.
1. A GitHub account¶
Sign up at https://
GitHub may ask you to turn on two-factor authentication (2FA). Do it now with an authenticator app, rather than being locked out halfway through the workshop.
2. Install Git¶
Download Git for Windows from https://
It installs two things you will use:
Git Bash, a terminal. Use it for every command in this workshop, so the commands work exactly as written (not PowerShell or
cmd).Git Credential Manager, which signs you in to GitHub through your browser the first time you push.
Open Terminal and type git --version. If Git is not installed, macOS
offers to install the Command Line Developer Tools: accept.
With Homebrew you can instead run brew install git.
Use your package manager, for example on Ubuntu or Debian:
sudo apt update && sudo apt install gitCheck it works. You need version 2.28 or newer:
git --version3. Tell Git who you are¶
Every commit records an author. Run these once, with your name and the email of your GitHub account:
git config --global user.name "Your Name"
git config --global user.email "you@example.com"
# Name the first branch "main", like GitHub does
git config --global init.defaultBranch main
# Make "git pull" merge, so it never stops to ask how
git config --global pull.rebase falseIf you use VS Code, make it Git’s editor too, instead of the default vim,
which can be hard to exit:
git config --global core.editor "code --wait"4. Let Git sign in to GitHub¶
GitHub does not accept your password from the terminal. The simplest way to sign in is the GitHub CLI:
Install it from https://
cli .github .com (Windows: run the installer; macOS: brew install gh; Linux: see the instructions on that page).Run:
gh auth loginAnswer: GitHub.com, then HTTPS, then Yes to “Authenticate Git with your GitHub credentials”, then Login with a web browser. Copy the one-time code and paste it into the page that opens.
Check:
gh auth status
5. A code editor¶
Any editor works. VS Code is a good choice: it shows Git changes and helps you resolve merge conflicts with one click.
6. Optional: Python and Docker¶
You can complete the whole workshop without these, because GitHub runs the tests and builds the Docker image for you in the cloud. Install them if you also want to run the app on your own machine.
Python 3.10 or newer, from https://
www .python .org /downloads/, to run the app and its tests locally. Docker Desktop, from https://
www .docker .com /products /docker -desktop/, to run containers locally in Part 3. Check it with: docker run hello-world
✅ Ready? Check every line¶
I can sign in at https://github.com, and I know my username.
git --versionprints 2.28 or newer.git config --global user.emailprints the email of my GitHub account.gh auth statussays I am logged in (or I am on Windows and will use Git Credential Manager).I know how to open a terminal (Git Bash on Windows) and an editor.
Optional:
docker run hello-worldprints “Hello from Docker!”.
If a line fails, ask in the workshop chat before the session starts.