Part

Git host

You might say: code host, repository host, forge, GitHub

A service that stores Git repositories and hosts their review objects, such as pull requests, checks and merge controls.

What it does

Turns workspace changes into a reviewable change and records the events and gates that govern merging.

Ask

Where are the branch, diff, checks, review, identity, and merge decision recorded?

Typical

All-in-one platform, suite module, self-hosted forge, review-first system, agent-native host, or Git storage used by a separate run service.

Trouble

Runs cannot push, reviews are detached from the diff, checks are missing, or an identity can bypass merge controls.

What to look for

1. Repository, branch, and commit pages
2. A pull request with a diff and checks
3. A merge control beside required gates

Parts

• Pull request: A proposed change from one branch or repository into another, with a diff, discussion, checks, and a merge decision.
• Bot identity: The app, bot account, or token under which a run reads, writes, comments, and opens changes.
• Branch protection: Rules that constrain updates to important branches and require selected checks, reviews, or other conditions before merge.
• Webhook: An HTTP delivery that carries an event from one service to another so the receiver can act without polling.

Catalogue: Git host type

• All-in-one platform: Repository storage, code review, checks, and merge controls share one product surface. Pull requests and issues share the host's repository resources and controls.
• Suite module: Git hosting is one module in a larger development or work-management suite. The project surface combines files and tasks in one project.
• Self-hosted forge: The organization runs the repository and review service on its own infrastructure. Hosting, storage, and network policy stay under the organization's control.
• Review-first host: Review records organize changes through patch sets, labels, and approvals. The host makes review state central to contribution.
• Agent-native host: The host gives automated actors bot identities, event triggers, and native review operations. Agents can act in the same review and merge surfaces as people.
• Git storage for runs: Git repositories hold workflow definitions while another service executes their jobs. The host remains the source of code and workflow history.

Connections

• See also: Ticket tracker
• See also: Orchestrator

Sources

1. GitHub, REST API endpoints for pull requests, About pull requestsPull requests are a type of issue. Any actions that are available in both pull requests and issues, like managing assignees, labels, and milestones, are handled by the REST API to manage issues.
2. GitHub, About webhooks, About webhooks on GitHubWhen an event that your webhook is subscribed to occurs, GitHub will send an HTTP request with data about the event to the URL that you specified.
3. GitHub, About protected branches, Require status checks before mergingAfter enabling required status checks, all required status checks must pass before collaborators can merge changes into the protected branch.

Use it on your project

teardown-apply: hold "Git host" (git-host) from the teardown at https://teardownatlas.com/software-factory/ against my project

Paste it into a coding agent that has the teardown skills.

An AI agent wrote this map with the teardown skill. It can contain errors: check the sources before you rely on a part. About and legal