# Gitmoap documentation > How to use Gitmoap: hosting code, reviewing it, tracking the work around it and shipping it. Every page below links to its markdown. A `:::endpoint ` block names an API operation, documented at https://developers.gitmoap.com/operations/.md; the whole API is indexed at https://developers.gitmoap.com/llms.txt. ## Getting started - [Getting started](https://docs.gitmoap.com/getting-started.md): New to Gitmoap? Start here. Each page below takes you from nothing to something working, in order, with no decisions to make along the way. - [Your first repository, end to end](https://docs.gitmoap.com/getting-started/first-repository.md): Go from a signed-in account to a repository with your code in it and a pipeline that runs on it. - [Install the command-line tools](https://docs.gitmoap.com/getting-started/install.md): Gitmoap ships two command-line programs, and you want both. ## Guides - [Guides](https://docs.gitmoap.com/guides.md): One page per feature. Each tells you what the feature is for, what you need before you start, how to do the things people actually do with it, and what to do… - [Access tokens](https://docs.gitmoap.com/guides/access-tokens.md): An access token is a credential you hand to something that cannot open a browser — a CI job, a deploy script, a bot, a git client on a build machine. - [Access](https://docs.gitmoap.com/guides/access.md): Access is who can do what on a group or a repository. You give it with a grant: one person, service account or team, one role, one group or repository. - [Audit log](https://docs.gitmoap.com/guides/audit-log.md): The audit log answers who did what, to which resource, and when — for every change made through Gitmoap, every sign-in, every push and clone, and every read of… - [Billing and plans](https://docs.gitmoap.com/guides/billing.md): During the Beta, Gitmoap is free of charge and takes no payment: every organisation is on the Free plan, and the checkout, billing portal and invoices… - [Branches](https://docs.gitmoap.com/guides/branches.md): A branch is a named pointer to a commit, and in Gitmoap it lives in git exactly as it does on your laptop — there is no separate copy of it in a database to… - [How the CLI reaches Gitmoap](https://docs.gitmoap.com/guides/client-config.md): gitmoap and git-remote-gitmoap connect to Gitmoap on their own. - [Your dashboard](https://docs.gitmoap.com/guides/dashboard.md): Your dashboard is the screen that tells you what to do next. - [Diffs and comparisons](https://docs.gitmoap.com/guides/diffs.md): See exactly what changed. You can read what a single commit introduced, what a merge request would land, what separates any two branches, every file a change… - [Edit files in the browser](https://docs.gitmoap.com/guides/editing.md): You can change a repository without cloning it. Edit a file, add one, delete, move or rename one, or make a script executable — then commit the change straight… - [Groups](https://docs.gitmoap.com/guides/groups.md): A group is a namespace: a name in a path, a place repositories live, and the level at which you hand out access once instead of repository by repository. - [Issues](https://docs.gitmoap.com/guides/issues.md): Tracking work next to the code it changes. The work-items page is the one to read first; the rest go deeper into one part of it. - [Blueprints](https://docs.gitmoap.com/guides/issues/blueprints.md): Every team has a shape for a kind of work that never reaches the tracker: a new endpoint also needs a metric, a test, an access rule and a page of… - [Linking work to code](https://docs.gitmoap.com/guides/issues/code-links.md): Write Fixes #412 in a commit message and Gitmoap records the link, then closes the work item when that commit reaches the branch your product ships from. - [Work item discussion](https://docs.gitmoap.com/guides/issues/discussion.md): Every work item carries a discussion: a list of comments, each of which can be a thread with replies underneath it. - [Proof of Done](https://docs.gitmoap.com/guides/issues/proof-of-done.md): A work item's Definition of Done is a list of acceptance criteria, and on Gitmoap most of them can decide themselves. - [Work items](https://docs.gitmoap.com/guides/issues/work-items.md): A work item is one piece of work — a bug, a story, a task, an epic — filed against a repository or a group, tracked through a status you name, and connected to… - [Merge requests](https://docs.gitmoap.com/guides/merge-requests.md): Proposing a change, getting it reviewed, and landing it. Start with the first page and branch out as you need to. - [Approval rules](https://docs.gitmoap.com/guides/merge-requests/approvals.md): An approval rule says who has to approve a merge request before it can merge, and how many of them. Two people from the Release team for release/. - [Merge request discussion](https://docs.gitmoap.com/guides/merge-requests/comments.md): Discussion is where a merge request stops being a diff and becomes a decision. - [Merge requests](https://docs.gitmoap.com/guides/merge-requests/merge-requests.md): A merge request proposes to merge one branch into another, and holds everything that decides whether it should happen: the commits it carries, the reviews, the… - [Reviews and approvals](https://docs.gitmoap.com/guides/merge-requests/reviews.md): A review is how a merge request gets a second pair of eyes before it lands. - [Merge request settings](https://docs.gitmoap.com/guides/merge-requests/settings.md): Merge request settings are a repository's merge policy: how a merge request lands in git, whether its commits may be squashed, and what else has to be true… - [Cloud authentication from a pipeline](https://docs.gitmoap.com/guides/oidc.md): Deploy from a pipeline into your own AWS account with no access key stored anywhere. - [Getting set up](https://docs.gitmoap.com/guides/onboarding.md): The getting-started checklist tells you what is left before your account is genuinely usable: a repository of your own, something pushed into it, and a git… - [Package registries](https://docs.gitmoap.com/guides/package-registries.md): Publish private npm, Cargo and PyPI packages to a group and install them with the tools you already have. - [Pipelines](https://docs.gitmoap.com/guides/pipelines.md): Building, testing and shipping your code. Start with the pipelines page; components are how you stop writing the same pipeline twice. - [Pipeline components](https://docs.gitmoap.com/guides/pipelines/components.md): A pipeline component is a reusable fragment of a pipeline — a few nodes, the edges between them, the ports it exposes at its edge and the parameters it takes… - [Pipelines](https://docs.gitmoap.com/guides/pipelines/pipelines.md): A pipeline builds, tests and ships the code in a repository. - [Providers](https://docs.gitmoap.com/guides/providers.md): A provider is a step a pipeline can run — checking out code, building an image, deploying to a cloud. - [Provider policy and administration](https://docs.gitmoap.com/guides/providers/provider-governance.md): Decide which pipeline steps your organisation is willing to run at all. - [Publishing a provider](https://docs.gitmoap.com/guides/providers/publishing-providers.md): A provider packages pipeline capabilities — a build step, a deploy step, a notifier — as container images plus a manifest saying what each one takes in, what… - [Using providers](https://docs.gitmoap.com/guides/providers/using-providers.md): A provider is a step your pipeline can run — cloning a repository, building an image, pushing it to a registry, deploying it, telling a channel it worked. - [Releases](https://docs.gitmoap.com/guides/releases.md): Cut a release when a commit stops being a commit and becomes a version other people depend on. - [Repositories](https://docs.gitmoap.com/guides/repositories.md): A repository holds your code and everything the platform knows about it: who may read and write it, what it is written in, who has contributed, and every… - [Repository rules](https://docs.gitmoap.com/guides/repository-rules.md): Repository rules are how you stop the things you do not want to happen from happening at all, rather than finding out afterwards. - [Custom roles](https://docs.gitmoap.com/guides/roles.md): The five built-in roles — Guest, Reporter, Developer, Maintainer and Owner — cover most of what people do. - [SCIM provisioning](https://docs.gitmoap.com/guides/scim.md): SCIM lets your identity provider — Okta, Microsoft Entra ID, OneLogin, JumpCloud or any other that speaks SCIM 2.0 — tell Gitmoap who works at your… - [Search](https://docs.gitmoap.com/guides/search.md): Type what you remember and get back everything you can read that matches it: work items, merge requests, comments, releases, repositories, groups, services… - [Service accounts](https://docs.gitmoap.com/guides/service-accounts.md): A service account is an identity nobody logs into — a deploy bot, a release script, a nightly job — that belongs to a group or a single repository instead of… - [Service catalog](https://docs.gitmoap.com/guides/service-catalog.md): The catalog answers the four questions nobody can answer from a repository list: what do we run, who owns it, where is it deployed, and is it any good? - [Spec index](https://docs.gitmoap.com/guides/specs.md): Gitmoap reads the markdown you already keep in your repository — everything under specs/, docs/, legal/ and blog/ — and turns it into data you can ask… - [Single sign-on](https://docs.gitmoap.com/guides/sso.md): Single sign-on connects your organisation to your own identity provider — Okta, Microsoft Entra ID, OneLogin, Ping, Google Workspace, or any SAML 2.0 or OpenID… - [Teams](https://docs.gitmoap.com/guides/teams.md): A team is a named set of people in your organisation — Backend, SRE, Security reviewers. A team can do nothing by itself. - [Your account](https://docs.gitmoap.com/guides/users.md): Your account is the identity everything else hangs off: the name on your commits and comments, the person a merge request is assigned to, the owner of your… - [Webhooks](https://docs.gitmoap.com/guides/webhooks.md): A webhook makes Gitmoap call your own HTTPS endpoint the moment something happens — a push lands, a merge request is merged, a work item closes — so your… - [Wiki](https://docs.gitmoap.com/guides/wiki.md): A wiki is the documentation that belongs to a repository or a group but is not part of its code: the explanation of how something works, the decision nobody…