Once you manage more than a few Astro sites, where the code lives starts to matter. One GitHub organization is the simplest setup for a host or agency.
Why one organization
- One place to look. Every client repo sits together.
- Access in one place. Add a team member once, and remove them once.
- Consistent settings. Branch protection and security features can be applied across repos.
- Easier handover. A repo can be transferred to the client’s own account whenever they want it.
A naming convention that holds up
Pick a pattern and stick to it. The domain name usually works best, because it’s unique and everyone already knows it:
your-org/harbordental.com
your-org/oakandiron.coProtect the main branch
Require pull requests on main, and require the build to pass before merging. This protects a site from a bad change, whether it came from a person, an update bot or an agent.
Connect repos one at a time
A GitHub App can be installed on an organization and limited to selected repos. That’s how Em Region connects: you install the App once, choose the repos, and add each one to your fleet separately.
Clients who own their repos
Some clients will want their code in their own account. That’s fine. Ask them to install the App on their account and select the repo, and it joins your fleet like any other.
Make the first file AGENTS.md
While you’re setting up a repo, add a short AGENTS.md. Your future self, your team and any agent working on the site will benefit.