Watch · Hands-On Guide, Exercise 2

Your First Pull Request

2:31 · Hands-On Guide

Made by AI agents — script drafted from the book, AI narration, animation written as code — and steered by the author, Rasmus Bornhøft Schlünsen.

Transcript

What the film says

In exercise one, you set up your workshop. Now you use it. You fork a real book, write an honest review of one chapter, and send it to the author as a pull request. This isn't a simulation. Your pull request shows up on GitHub, where real people will read it.

Step one: fork. A fork is your own copy of someone else's project, stored on GitHub. A single command makes that copy, downloads it to your machine, and links it back to the original.

Before you change anything, look around. Open chapter one and read it, all of it. Form your own opinions. That's the whole point. And notice the Claude dot M D file: plain notes that an agent reads the moment it starts in this folder.

Next, make a branch. A branch is a safe parallel universe, where you can change anything without touching the main copy. Ten people editing one document at once is chaos. With branches, everyone works on their own, and the changes merge one at a time.

Now write your review in a new file. Start from the template: first impressions, what worked, what could be better, who it's for, and a rating out of five. Don't overthink it. One genuine paragraph per heading beats a polished essay.

Then add the file. Before you commit, look at exactly what you're about to record. Nothing gets committed that you haven't read. Commit it, with a message. Then push your branch up to your fork.

And now the moment. A pull request is a proposal. It says: I made a change on my copy. Would you like to merge it into yours? The author reads it, and may leave a comment. Once it's merged, your review is a permanent part of the project's history.

You can also hand the Git work to an A I agent. Ask for a plan first, and tell it to wait until you say go. When it asks to run git push, or G H P R create, look before you approve. Those publish your work to the internet. And a file you didn't write is untrusted input. If the agent suddenly wants something you never asked for, stop and look.

Fork, branch, write, commit, push, propose. Every contribution to every major project follows that path, and you just walked it, for real. Let the agent help you find the words, but keep the opinions yours. Next up: your first A I generated project.