Back to Thinking
Nov 17, 2026|4 min read

One GitHub repository or several?

When people start building tools they want to share, GitHub keeps every version and lets several people work on the same files. The first question is whether everything goes in one place or each tool gets its own. Start with one.

Once a few people in a team are building tools they want to share, GitHub keeps every version and lets several people work on the same files. The first question is whether everything goes in one place or each tool gets its own.

Four words you'll need

That's all the vocabulary. Claude does the rest when you ask in plain words.

Four words you'll need

Repository

A project folder that remembers every version and who changed what.

Organisation

Your company's space on GitHub. Decides who sees each repository.

Save and share

Keeps a version with a one-line reason and sends it to the others.

Get latest

Brings everyone else's changes onto your computer.

One repository or several

Both work. They suit different stages.

One repository or several

One team repository

team-ai/
CLAUDE.md
library/ instructions, scorecards
tools/
report-review/
translation/
  • One thing to set up, one place to look
  • Tools reuse the library
  • Everyone sees everything

One repository per tool

team-library/
report-review/
translation/
each with its own CLAUDE.md,
people and history
  • You choose who sees each tool
  • A tool can run or leave on its own
  • More to set up and remember

Start with one. A tool moves into its own repository when it needs to, and keeps its history.

Start with one

A small team with tools that are a few weeks old is better off in one repository. Each tool gets a folder. A tool moves into its own repository when it needs to, and keeps its history when it does. Client documents stay on the shared drive, never on GitHub.

The organisation belongs to your company. If we help set it up, we join while we work together and leave when you're ready. Two of you are owners, so it never depends on one person.

When a tool gets its own repository

If none of these is true, the tool stays a folder. If one is, ask Claude to move it out.

  1. Different people. Only some of you should see it, or a freelancer needs it and nothing else.
  2. It runs on its own. It becomes a website, a service or something on an office machine.
  3. It leaves the firm. You hand it to a client or a partner.
  4. It's slowing everyone down. Big files, or lots of changes nobody else needs.

Move tools/<tool name> into its own repository in our organisation, with its history. Give it a CLAUDE.md that points to our library, then remove the folder here and say where it went in the README.

Your account

Ten minutes each. Use your work email.

  1. Sign up at github.com with your work email. The free plan is all you need.
  2. Add a passkey under Settings, Password and authentication. It's your fingerprint or face, so no extra code to type.
  3. Send your username to whoever owns the organisation. They add you and you accept the email.
  4. Sign in to VS Code with GitHub: the person icon at the bottom left.

Bring your project in

Put the repository in a plain folder such as Documents/GitHub. Not in Google Drive, OneDrive, Dropbox or iCloud: the sync and GitHub both write to the same hidden files and damage each other.

Clone our team repository <name> into Documents/GitHub and open it.

Copy my project from <paste the path> into tools/<tool name>/. Before you save anything, check it for client names, personal details, passwords, API keys and files over 50 MB, and show me what you found. Write a short README.md: what the tool does, how to start it and who looks after it. Then save and share with the message "Add <tool name>".

If Claude finds something, it goes on the shared drive or on the list of files GitHub ignores, and the tool reads it from there. Every day after that, say "get latest" when you start and "save and share: <what you changed>" when you're done. If two of you changed the same lines, Claude says so and suggests how to combine them. Read it, then say which version to keep.

When a tool in the repository is ready for people outside the team, it goes through a check before it goes live. That's in From your sandbox to something customers use.