← All blueprints

GitHub

1 guide

Guides for storing and syncing your code with GitHub.

About GitHub

GitHub is where your code lives once you move past a single local project, and it is also where most people building with AI tools get stuck for the first time: connecting a repo, resolving a sync conflict, or understanding what a pull request actually does. These guides focus on the exact moments people get confused, not a full course on git.

Connecting your project for the first time

Linking a project to GitHub is a one time setup that causes disproportionate confusion the first time you do it, especially when an AI builder tool is also pushing commits on your behalf.

What to do when something conflicts

A merge conflict looks alarming the first time you see it, but it almost always comes down to two changes touching the same lines. These guides show the calm, repeatable way to resolve it.

Commit in small, working chunks: Committing after every small working change, rather than one giant commit at the end of the day, makes it far easier to undo a mistake later.
Read the conflict markers before panicking: The lines between conflict markers in a file tell you exactly what is different. Read them slowly before deciding what to keep.
Do I need to know git commands to use GitHub with an AI builder?

Not for most day to day use. Many AI builder tools handle commits and pushes automatically. These guides cover the moments where you do need to step in directly.

What is a pull request in simple terms?

A pull request is a request to merge one set of changes into your main codebase, along with a place to review exactly what changed before it happens.

Browse all blueprints