# Git

Doltgres implements Git-style version control on tables instead of files.

Doltgres adopts the Git-interface to version control. There are [commits](/concepts/git/commits.md),[branches](/concepts/git/branch.md), [merges](/concepts/git/merge.md), and all the other Git concepts you are familiar\
with. If you know Git, Doltgres will feel very familiar because conceptually, Doltgres is modeled on\
Git.

In SQL, Git read operations are modeled as [system\
tables](/reference/version-control/dolt-system-tables.md). Git write operations are modeled\
as [system functions](/reference/version-control/dolt-sql-functions.md). But\
conceptually, all the Git concepts you are familiar with extend to SQL.

In this section we explore the following Git concepts and explain how they work in Doltgres:

1. [Commits](/concepts/git/commits.md)
2. [Log](/concepts/git/log.md)
3. [Diff](/concepts/git/diff.md)
4. [Branch](/concepts/git/branch.md)
5. [Merge](/concepts/git/merge.md)
6. [Conflicts](/concepts/git/conflicts.md)
7. [Remotes](/concepts/git/remotes.md)
8. [Working Set](/concepts/git/working-set.md)


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.doltgres.com/concepts/git.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.