# GitCafe > GitCafe is a Git forge for hosting repositories and collaborating on code. It works on its own; a repository can also sync one- or two-way with GitHub, including issues, pull requests, reviews and comments. Start with [What can I do with GitCafe?](https://staging.git.cafe/docs/agent-workflows.md): reading public repositories without an account, choosing an access path, collaboration and integrations. A repository's `///llms.txt` gives an overview of that repository. ## Docs - [GitCafe documentation · GitCafe Docs](https://staging.git.cafe/docs/index.md): GitCafe is a home for your Git repositories, with pull requests, stacked changes, issues and CI results in one place. These guides show you how to use it. - [Quickstart · GitCafe Docs](https://staging.git.cafe/docs/getting-started/quickstart.md): Create an account, push your first repository and open a pull request. - [Clone and push with Git · GitCafe Docs](https://staging.git.cafe/docs/getting-started/git-access.md): GitCafe repositories work with any Git client over HTTPS or SSH. Copy a repository's address from its Code button: the HTTPS tab gives https://git.cafe// and the SSH tab gives git.cafe:/. The .git suffix is optional. - [Install the CLI · GitCafe Docs](https://staging.git.cafe/docs/getting-started/cli.md): cafe is GitCafe's command-line tool. It signs you in, sets up Git credentials, and manages repositories, pull requests, stacks, issues and more from the terminal. Every command is listed in the CLI reference. - [What can I do with GitCafe? · GitCafe Docs](https://staging.git.cafe/docs/agent-workflows.md): This page is a map for coding agents and other tools: how to read GitCafe without an account, how to authenticate, and where each workflow is documented. Replace , and numbers with real values. - [Create a repository · GitCafe Docs](https://staging.git.cafe/docs/repositories/repository-create.md): You need a verified email address to create a repository. To bring an existing project from GitHub instead, see GitHub import. - [Branches · GitCafe Docs](https://staging.git.cafe/docs/repositories/branches.md): Open a repository's Branches tab to browse its branches, start a pull request or create and delete branches. You need read access to the repository. - [Tags · GitCafe Docs](https://staging.git.cafe/docs/repositories/tags.md): Open a repository's Tags tab to find a tagged version of its code. You need read access to the repository. - [Browse history and blame · GitCafe Docs](https://staging.git.cafe/docs/repositories/commits.md): Read a repository's commit history, inspect a single commit, and see who last changed each line of a file. You need read access to the repository. - [Search code · GitCafe Docs](https://staging.git.cafe/docs/repositories/code-search.md): Search the files of one branch or tag in a repository. Open the Search tab in the repository header, or ///search. - [Manage repository access · GitCafe Docs](https://staging.git.cafe/docs/repositories/repository-access.md): Repository admins decide who can work on a repository under Settings → Access. Organization members also get the organization's default repository permission. - [Protect branches and tags with rulesets · GitCafe Docs](https://staging.git.cafe/docs/repositories/repository-rulesets.md): A ruleset protects matching branches or tags: it can require pull requests, reviews and passing checks, or block deletion and force pushes. Repository admins manage rulesets under Settings → Rulesets. Organizations and teams can also define rulesets that apply to their repositories. - [Repository settings · GitCafe Docs](https://staging.git.cafe/docs/repositories/repository-settings.md): Open Settings → General in a repository to change its details, visibility and default branch, transfer it, restore deleted branches or delete it. The Settings tab is shown to maintainers and admins. - [Mirror a branch with another Git server · GitCafe Docs](https://staging.git.cafe/docs/repositories/git-mirrors.md): A Git mirror keeps one branch in sync with a branch on another Git server: pull changes into GitCafe, push them out, or both. Maintainers set mirrors up under Settings → Git mirrors. - [Star a repository · GitCafe Docs](https://staging.git.cafe/docs/repositories/repository-stars.md): Star a repository to bookmark it and show your appreciation. The Star button and the star count are in every repository header. - [Open a pull request · GitCafe Docs](https://staging.git.cafe/docs/pull-requests/open.md): A pull request proposes merging the commits on one branch (the source) into another (the target). Open one when your branch is ready for review, then review and merge it. - [Review a pull request · GitCafe Docs](https://staging.git.cafe/docs/pull-requests/review.md): Open a pull request from the repository's Pull requests tab. Anyone with read access can read it; reviewing, merging and moderating depend on your repository role. - [Merge a pull request · GitCafe Docs](https://staging.git.cafe/docs/pull-requests/merge.md): Merge an open pull request from the merge button at the bottom of its Conversation tab. You need permission to merge, and the repository's rulesets must be satisfied. - [Stacked pull requests · GitCafe Docs](https://staging.git.cafe/docs/pull-requests/stacks.md): A stack is an ordered chain of open pull requests in one repository. Each pull request targets the branch of the one below it, and the bottom one targets the landing base, such as main. Use a stack to split a large change into small reviewable steps that depend on each other. - [Track work with issues · GitCafe Docs](https://staging.git.cafe/docs/issues/issues.md): Issues record bugs, tasks and ideas for a repository. Open a repository's Issues tab to find, create and discuss them. You need access to the repository. - [Pin and lock issues · GitCafe Docs](https://staging.git.cafe/docs/issues/pin-and-lock.md): Users with triage access to a repository can pin important issues and lock heated or finished conversations. Both controls are in the issue sidebar. - [Labels · GitCafe Docs](https://staging.git.cafe/docs/issues/labels.md): Labels categorize issues and pull requests. Each repository has its own set, managed under Settings → Labels. The label picker on an issue or pull request links there through Manage labels. - [Milestones · GitCafe Docs](https://staging.git.cafe/docs/issues/milestones.md): A milestone groups issues and pull requests toward a shared target, such as a release, and tracks how many are done. Open Milestones from the issue list, or Manage milestones from the milestone picker. - [Account settings · GitCafe Docs](https://staging.git.cafe/docs/account/account-settings.md): Open Settings → Account to manage your email address, password, passkeys and signed-in sessions, or to close your account. - [Recover your account · GitCafe Docs](https://staging.git.cafe/docs/account/password-recovery.md): If you forget your password, reset it by email. If your account requires a passkey and you lose every passkey, use a recovery code. - [Your public profile · GitCafe Docs](https://staging.git.cafe/docs/account/profile.md): Your profile at / shows your avatar, display name, bio and, when set, your company, location and website, followed by your pinned and public repositories. Anyone can view it without signing in. Organizations have profiles at / too. - [Appearance · GitCafe Docs](https://staging.git.cafe/docs/account/appearance.md): Open Settings → Appearance and choose a Theme: Light, Dark or System, which follows your operating system. The change applies immediately. - [SSH keys · GitCafe Docs](https://staging.git.cafe/docs/account/ssh-keys.md): Add an SSH key to push and pull over SSH, to sign commits, or both. Open Settings → SSH Keys. - [GPG keys · GitCafe Docs](https://staging.git.cafe/docs/account/gpg-keys.md): Add your GPG public key so commits and tags you sign show as Verified. Open Settings → GPG Keys. - [Personal access tokens · GitCafe Docs](https://staging.git.cafe/docs/account/personal-access-tokens.md): A personal access token lets scripts, CI jobs and tools use the REST API or Git over HTTPS as you, with only the permissions you grant. Tokens start with gct_ and always expire. Manage them at Settings → Tokens. - [Approve a CLI sign-in · GitCafe Docs](https://staging.git.cafe/docs/account/device-authorization.md): Command-line tools such as the cafe CLI sign in with a device code. The tool shows a code like ABCD-EFGH and opens /device in your browser, usually with the code filled in. - [Billing and plans · GitCafe Docs](https://staging.git.cafe/docs/account/billing.md): Your personal account and each organization have their own plan. See the personal plan at Settings → Billing, and an organization's at Billing in its settings (/orgs//settings/billing). Organization owners and admins can view billing; only owners can change it. - [Organizations · GitCafe Docs](https://staging.git.cafe/docs/organizations/organizations.md): An organization owns repositories on behalf of a group of people, with shared roles, teams, rulesets and billing. Every account also has a personal namespace with the same handle as the user. - [Organization members · GitCafe Docs](https://staging.git.cafe/docs/organizations/organization-members.md): Owners and admins manage who belongs to an organization on its Members tab, /orgs//members. - [Teams · GitCafe Docs](https://staging.git.cafe/docs/organizations/teams.md): Teams group organization members and give them a shared role on repositories. Teams can be nested: a child team's path joins its parents' handles with dots, such as eng.web. Open the Teams tab of an organization. - [Organization settings · GitCafe Docs](https://staging.git.cafe/docs/organizations/organization-settings.md): Owners and admins manage an organization at /orgs//settings. The settings pages are General, Billing, Webhooks, Rulesets and Integrations. - [Connect Buildkite · GitCafe Docs](https://staging.git.cafe/docs/ci/buildkite.md): GitCafe shows Buildkite builds on a repository's CI tab and as checks on pull requests. Builds run in Buildkite; GitCafe does not start or schedule them. Connecting takes two steps: an integration for your account or organization, then a pipeline for each repository. - [Read CI results and logs · GitCafe Docs](https://staging.git.cafe/docs/ci/checks-and-logs.md): Once Buildkite is connected, GitCafe shows build results on the repository's CI tab and as checks on pull requests and commits. - [Import and sync from GitHub · GitCafe Docs](https://staging.git.cafe/docs/integrations/github-sync.md): Bring repositories from GitHub into GitCafe with their issues, pull requests, reviews and comments, and optionally keep both sides in sync. Imports use the GitCafe GitHub App, including for public repositories. GitHub is optional: repositories created in GitCafe need no GitHub account. - [Webhooks · GitCafe Docs](https://staging.git.cafe/docs/integrations/webhooks.md): Webhooks are in beta: event coverage and payload fields may still change. A webhook sends a signed HTTPS request to your server when something happens in a repository or organization, such as a push, a new issue or a merged pull request. - [Connect an MCP app · GitCafe Docs](https://staging.git.cafe/docs/account/mcp-connections.md): GitCafe runs an MCP server at https://git.cafe/mcp, so AI tools such as Claude and ChatGPT can read repositories and, with your approval, work on issues and pull requests. Each connection is limited to the repositories and permissions you approve. - [CLI reference · GitCafe Docs](https://staging.git.cafe/docs/reference/cli.md): Every cafe command, grouped by area. Run cafe --help for all of a command's options. To install the CLI and sign in, see install the CLI. - [REST API · GitCafe Docs](https://staging.git.cafe/docs/reference/api.md): The GitCafe REST API lives at https://git.cafe/api. Everything you can do in the browser goes through it, and most of it is open to your own tools. - [API rate limits · GitCafe Docs](https://staging.git.cafe/docs/reference/rate-limits.md): Every request to /api and /mcp counts against a budget. Signed-in requests count against your account; anonymous requests count against your network address. This page lists the limits, how to read them and what to do when you hit one. - [Read GitCafe as Markdown · GitCafe Docs](https://staging.git.cafe/docs/reference/markdown.md): Every guide, and most repository pages, can be read as Markdown. This is handy for scripts, coding agents and anything that prefers text to HTML. ## Site - [GitCafe — Your code. All together.](https://staging.git.cafe/index.md): Git hosting, code review, and stacked pull requests. Use it on its own, or keep it in sync with GitHub. Work in the browser or with the Cafe CLI. - [Legal · gitcafe](https://staging.git.cafe/legal/index.md): GitCafe's terms, privacy, acceptable use, and copyright policies. - [Acceptable Use Policy · gitcafe](https://staging.git.cafe/legal/acceptable-use.md): Rules protecting GitCafe, its users, and the public from abuse. - [Copyright Policy · gitcafe](https://staging.git.cafe/legal/copyright.md): How GitCafe handles copyright notices and counter-notices. - [Privacy Policy · gitcafe](https://staging.git.cafe/legal/privacy.md): How GitCafe collects, uses, shares, and protects information. - [Terms of Service · gitcafe](https://staging.git.cafe/legal/terms.md): The terms that govern use of GitCafe. - [Pricing · gitcafe](https://staging.git.cafe/pricing.md): GitCafe is free for public repositories, and private repositories are free during the public beta. Pro is $20 per month; Team is $40 per seat per month with 5× rate limits, or $80 with 10×. - [Create an account](https://staging.git.cafe/auth/sign-up.md): Create a free GitCafe account: start fresh or sync with GitHub, then work in the browser, the Cafe CLI, MCP or the API. - [Sign in](https://staging.git.cafe/auth/sign-in.md): Sign in to GitCafe. ## Optional - [All public content](https://staging.git.cafe/llms-full.txt): Site pages and every guide in one file. - [OpenAPI specification](https://staging.git.cafe/api/openapi/json): Generated REST API schemas. - [MCP server card](https://staging.git.cafe/mcp/server-card): Remote MCP server identity and tools.