> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/glossary/g/git.md).

# Git

A distributed version-control system for tracking changes in source code during software development.

Git is a distributed version control system that tracks changes in source code during software development. Created by Linus Torvalds in 2005, Git allows multiple developers to work on the same codebase simultaneously, maintaining a complete history of all changes and enabling branching, merging, and collaboration.

Git stores the complete repository history on every developer's machine, enabling offline work and fast operations. Key concepts include commits (snapshots of changes), branches (parallel lines of development), merges (combining branches), and remotes (connections to shared repositories). Hosting platforms like GitHub, GitLab, and Bitbucket provide centralized collaboration features on top of Git.

In API and serverless development, Git is essential for managing both application code and infrastructure configuration. API gateway configurations, routing rules, and deployment scripts are stored in Git repositories, enabling version tracking and code review. GitOps workflows use Git as the single source of truth for infrastructure state, automatically deploying changes when they are pushed to the repository.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.serverlessapigateway.com/glossary/g/git.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.