# GitCafe documentation > Guides to using GitCafe. Feature availability and limitations are documented per workflow. ## Start here - [GitCafe documentation](https://git.cafe/docs/index.md): Create repositories, collaborate on changes, and manage your account and organizations. Start with creating a repository or importing from GitHub. ## Repositories - [Creating a repository](https://git.cafe/docs/repositories/repository-create.md): Open /new, or use the creation form in the repository directory. Sign in and verify your email before creating a repository. - [Branches](https://git.cafe/docs/repositories/branches.md): Open a repository's Branches tab to browse branches or find work to review. You need read access to the repository. The history icon opens Deletion activity. - [Tags](https://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. The history icon opens Deletion activity. - [Commits](https://git.cafe/docs/repositories/commits.md): Open Commits from a repository's Code toolbar to browse its history. You need read access to the repository. - [Inspect a commit](https://git.cafe/docs/repositories/commit.md): Select a commit's hash or summary in repository history to read its message and inspect the changes it made. You need read access to the repository. - [Code search](https://git.cafe/docs/repositories/code-search.md): /{owner}/{repo}/search searches the files of one branch or tag for a pattern. Open it from the Search tab in the repository header. - [Repository access settings](https://git.cafe/docs/repositories/repository-access.md): /{owner}/{repo}/settings/access (the Access entry in repository settings) manages who can reach a repository directly. Only repository admins can load it; everyone else sees the server's permission error. - [Repository rulesets](https://git.cafe/docs/repositories/repository-rulesets.md): /{owner}/{repo}/settings/rulesets (the Rulesets entry in repository settings) protects branches and tags. Only repository admins can manage it. - [Repository stars](https://git.cafe/docs/repositories/repository-stars.md): Every repository header shows a Star button with the current star count next to the clone popover. - [Manage repository settings](https://git.cafe/docs/repositories/repository-danger-zone.md): Use Settings → General (///settings) to manage visibility, the default branch, transfers, retained branches and repository deletion. Administration requires the permissions described below. If settings change while you are editing, reload and review the current values before retrying. ## Collaboration - [Find pull requests](https://git.cafe/docs/collaboration/pull-requests.md): Open a repository's Pull requests tab to find changes awaiting review or look up a previous merge. Select a title to review the pull request. You need read access to the repository. - [Create a pull request](https://git.cafe/docs/collaboration/pull-request-create.md): /{owner}/{repo}/pulls/new opens a pull request. It is reached from New Pull Request on the pull request list and from New pull request on a non-default row of the branches page, which preselects that branch (?compare=). - [Review and merge a pull request](https://git.cafe/docs/collaboration/pull-request.md): Open a pull request from the repository's Pull requests tab. You need read access to see it; review, merge and moderation controls depend on your repository permissions. - [Review changes](https://git.cafe/docs/collaboration/pull-review-drafts.md): Batch inline comments into one review and submit them together, from the "Files changed" tab of a pull request. - [Stacked pull requests](https://git.cafe/docs/collaboration/stacks.md): A stack is an ordered set of open pull requests in one repository. Each pull request targets the previous one's source branch; the bottom pull request targets the landing base, such as main. Use a stack when a change depends on another change that has not yet merged. - [Track work with issues](https://git.cafe/docs/collaboration/issues.md): Open a repository's Issues tab to find work, report a problem, or follow a conversation. You need access to the repository. Select an issue title to read its description and discussion. - [Issue pinning and locking](https://git.cafe/docs/collaboration/issue-moderation.md): Moderators (users with triage rights on the repository) see two extra controls in the issue sidebar. - [Labels](https://git.cafe/docs/collaboration/labels.md): Repository labels live under Settings → Labels (/{owner}/{repo}/settings/labels). The issue and pull request sidebars link there from the label picker ("Manage labels"). - [Milestones](https://git.cafe/docs/collaboration/milestones.md): Milestones live at /{owner}/{repo}/milestones, reached from the Milestones button on the issue list or the "Manage milestones" link in the issue and pull request milestone picker. ## Your account - [Account settings](https://git.cafe/docs/account/account-settings.md): Open Settings → Account to manage your sign-in methods and signed-in devices. Sign in before changing these settings. - [Appearance](https://git.cafe/docs/account/appearance.md): Open Settings → Appearance and choose a colour theme from the Theme picker: Light, Dark or System (follows the operating system and switches live when it changes). The choice applies immediately. - [Public profiles](https://git.cafe/docs/account/public-profiles.md): / shows a user or organization's public profile: avatar, display name, handle, bio, and (when set) company, location, and website. Profiles are public; you do not need to be signed in. - [Edit your profile](https://git.cafe/docs/account/profile-management.md): Update the information people see on your public profile. Sign in and open Settings → Profile. - [Personal access tokens](https://git.cafe/docs/account/personal-access-tokens.md): /settings/tokens lists and issues tokens for the API, git over HTTPS and automation. Tokens start with gct_; the list only ever shows the last eight characters. - [Device authorization](https://git.cafe/docs/account/device-authorization.md): Command-line tools sign in through /device. The tool shows a short code such as ABCD-EFGH and opens this page, usually with the code already filled in. - [SSH keys](https://git.cafe/docs/account/ssh-keys.md): Open Settings → SSH Keys while signed in to add a key for Git authentication or commit signing. - [GPG keys](https://git.cafe/docs/account/gpg-keys.md): Open Settings → GPG Keys while signed in to add or remove a public signing key. - [Password recovery](https://git.cafe/docs/account/password-recovery.md): If you lose your password, /auth/recover can email you a link to set a new one. Email recovery is unavailable while Require a passkey is enabled: use your passkey to sign in. This setting is a passkey-only policy: password sign-in is rejected rather than followed by a second passkey step. Recovery also requires the deployment's mail service to be configured. - [Billing](https://git.cafe/docs/account/billing.md): /settings/billing shows the plan for your personal account; every organization has the same page at /orgs//settings/billing, listed as Billing in the settings navigation. Organization owners and admins can view billing. Only owners can change the plan or billing settings. ## Organizations - [Organizations](https://git.cafe/docs/organizations/organizations.md): An organization is a shared owner for repositories. Every account also has a personal organization with the same handle as the user. - [Organization members](https://git.cafe/docs/organizations/organization-members.md): /orgs//members lists who belongs to a non-personal organization. A personal organization has no members page and redirects to its overview. - [Accepting an organization invitation](https://git.cafe/docs/organizations/organization-invitations.md): Open the invitation link in the email sent by your organization. Sign in with the account the invitation was intended for. - [Organization settings](https://git.cafe/docs/organizations/organization-settings.md): /orgs//settings/general is available to owners and admins; the bare /settings path lands there. Other members see an access-denied page when opening a Settings URL directly; settings controls are not shown. The settings navigation includes General, Billing, Rulesets and Integrations. - [Teams](https://git.cafe/docs/organizations/teams.md): Organization teams group members and grant them a shared role on repositories. Teams nest: a team's path is its ancestors' handles joined with dots (eng.web), and that path is also its URL segment. ## Integrations - [GitHub import and synchronization](https://git.cafe/docs/integrations/github-sync.md): Open /import/github while signed in. The page offers public-source imports and repositories available through your connected GitHub account. Repository creation requires verified email and permission to create under the destination owner. - [Mirror a branch with another Git server](https://git.cafe/docs/integrations/git-mirrors.md): Repository maintainers can open Settings → Git mirrors at ///settings/mirrors to synchronize a branch with a remote Git repository. Each card labels the GitCafe and remote branches, names the direction, and explains which side wins a two-way conflict. - [Buildkite results and settings](https://git.cafe/docs/integrations/buildkite-ui.md): Connect Buildkite to see build results on repository CI pages and pull requests. Builds run in Buildkite; these settings do not start or schedule builds. ## Optional - [All documentation](https://git.cafe/docs/llms-full.txt): Combined guide text. - [OpenAPI specification](https://git.cafe/api/openapi/json): Generated API schemas.