Sikau

Project: Team workflow · Day 1 · about 30 min

Start the repo right

git init, a .gitignore that keeps secrets out, a first commit and a feature branch.

Real tools, one project

This combined project brings Git, TypeScript and Web essentials together the way a team uses them: you'll build a typed API client and a live search for the café, in a repository you set up yourself, then ship it with a reviewed, merged, tagged release.

  • Day 1: the repository (Git)
  • Day 2: typed data (TypeScript)
  • Day 3: a typed HTTP client (TypeScript + HTTP)
  • Day 4: fast, safe, accessible search (Web essentials)
  • Day 5: ship the release (Git, with a conflict)

What never goes in Git

Dependencies (node_modules/) are rebuilt from package.json, and secrets (.env) must never be pushed — once a key is in history, treat it as leaked. A .gitignore written *before* the first commit keeps them out for good.

git init
echo "node_modules/" > .gitignore
echo ".env" >> .gitignore
git status          # .env and node_modules are gone from the list
git add .
git commit -m "Initial commit"
git switch -c typed-client

The rest of this lesson

  • A professional first commitexplain
  • Branch from the startexplain
  • Ignored?predict
  • Commit or ignore?match
  • Set it upwrite code
  • Badge quizquiz
  • What you set uprecap

Continue this lesson free — run real code in your browser

Continue with Google

See all 5 lessons of Project: Team workflow