Lock In Lab Intern, rank 1 of 9

JR-1featureFirst of 3 Junior Dev tickets

Put it on a public URL

Takes
35 min in 3 steps
Checked
19 Nov 2026
min

Your estimate is optional. Your review compares it with how long it took; nothing is scored.

Nothing counts until someone else can open it. You'll push your project to GitHub and connect a free static host so every push publishes a new version.

This is the first ticket where something can break in public. That's on purpose.

You'll need A GitHub account and one free static host (Cloudflare Pages, Netlify or GitHub Pages). The tip splitter from INT-3, or any static page. Prices checked this month are on Tools.

Push to a new GitHub repository

Step 1 of 3, about 10 min

Create an empty repository on GitHub (no README, so it doesn't clash). Then:

git remote add origin https://github.com/<you>/tip-splitter.git
git push -u origin main

If your branch is called master, either push that or rename it with git branch -M main.

The part of a video worth watching for this step

YouTube, John Kim. Published Sep 2026.Checked 19 Nov 2026

Optional. The step counts when you've done it, whether or not you watch. Minutes from the creator's chapters; our notes on this video.

the usual mistake

A .gitignore rule that's too wide. data/ ignores every folder called data, anywhere. The site then builds on your laptop and not on the host. Anchor root folders: /data/. It happened to us in INC-03, "The deploy job was green and the site was down".

Connect a static host

Step 2 of 3, about 15 min

In your host's dashboard, choose "import from GitHub", pick the repository, and set the build command to nothing (or none) and the output folder to the one with index.html. Each host words this differently; the docs page for "deploy a static site" is the one you want.

The part of a video worth watching for this step

YouTube, Tech With Tim. Published Jul 2026.Checked 19 Nov 2026

Optional. The step counts when you've done it, whether or not you watch. Minutes from the creator's chapters; our notes on this video.

Prove that a push publishes

Step 3 of 3, about 10 min

Commit, push, wait for the host's build to finish, reload the URL. If the title didn't change, open the build log on the host before you ask the agent anything: the answer is usually there.

Paste this to your agent
Change the page title to 'Tip splitter v2'. Only that.

The part of a video worth watching for this step

YouTube, Jason Lee. Published May 2026.Checked 19 Nov 2026

Optional. The step counts when you've done it, whether or not you watch. Minutes from the creator's chapters; our notes on this video.

Check and ship

The whole ticket
Replace the URL with yours:
curl -sI https://your-site.example | head -1

It passes when The first line shows 200. The page title on that URL is 'Tip splitter v2'.

  • The page loads from a public https:// URL on someone else's phone.
  • A new commit pushed to GitHub shows up on that URL without you doing anything else.
  • Nothing secret in the repository.

No server checks your work in this version: you mark it, and your review says "Checked by you". Graded checks are planned for Plus.

Next: JR-2 Write house rules the agent actually follows

What do you see?

Pick the closest one. Each goes to what to try first and the incident it looks like.