> ## Documentation Index
> Fetch the complete documentation index at: https://docs.omni.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting content in git

> Diagnose why a commit or pull request for a document that requires a pull request to publish stopped, and what to change.

> [!NOTE]
>
> This feature is currently in beta. Reach out to Omni support to have it enabled for your organization.

Use this page to diagnose issues with documents that Omni writes to git. Each scenario describes what you're seeing, why it happens, and how to fix it. For issues with the git integration itself, refer to [Troubleshooting the Git integration](https://docs.omni.co/integrations/git/troubleshooting.md).

## The model's files overlap the content folder

**1. What you're seeing**

Committing a branch or opening a pull request fails with this error, and nothing is pushed:

```text wrap theme={null}
Documents are written to omni/content/ in the repository, which overlaps the model files at <model path>. Move that model to another path to write documents to git.
```

**2. Why it happens**

Omni reserves `omni/content/` at the repository root for document files. A model whose [model path](https://docs.omni.co/integrations/git/settings.md#model-path) is the repository root, `omni`, or a folder inside `omni/content` would put its own files in that folder. Omni stops the commit so the two sets of files cannot overwrite each other.

No model in the repository can commit documents while the overlap exists.

**3. How to fix it**

Change the [model path](https://docs.omni.co/integrations/git/settings.md#model-path) to a different folder, for example `omni/<model-name>/`, and commit again.

## A symbolic link stops the commit

**1. What you're seeing**

Committing a branch fails with this error, and nothing is pushed:

```
</Step>
<Step title="Why it happens" icon="question">
Omni doesn't follow symbolic links inside `omni/content/`, and doesn't change what a link points to. If a link sits anywhere on the path to a document's folder, Omni refuses to write.
</Step>
<Step title="How to fix it" icon="hammer">
Remove the symbolic link from `omni/content/` in the repository and commit again.
</Step>
</Steps>

## A document's folder holds only a stand-in file

<Steps>
<Step title="What you're seeing" icon="eye">
The pull request includes a document's folder, but `document.json` contains a short note instead of the document.
</Step>
<Step title="Why it happens" icon="question">
The document is a classic dashboard, which Omni cannot write to git. Omni commits a stand-in file for it so the pull request can still be reviewed and merged. The document itself is still published when the pull request is merged.
</Step>
<Step title="How to fix it" icon="hammer">
[Upgrade the classic dashboard](/visualize-present/dashboards/create#classic-dashboards). The next commit on the branch writes the dashboard's files in place of the stand-in. If you leave it as is, the document still publishes as usual on merge.
</Step>
</Steps>

## The pull request shows the workbook model folder as deleted

<Steps>
<Step title="What you're seeing" icon="eye">
The pull request diff for a document shows its `workbook-model/` folder as deleted, even though you didn't remove the workbook's model changes.
</Step>
<Step title="Why it happens" icon="question">
If Omni can't write a document's workbook model, it omits that folder and commits the rest. A `workbook-model/` folder from an earlier commit then shows as deleted in the diff.

<Note>
  This only applies to the workbook model. If Omni can't write the query model for one of the document's tabs, the commit stops and the error names the tab's `query-models/` folder.
</Note>
</Step>
<Step title="How to fix it" icon="hammer">
The document's workbook model changes aren't lost - they're still in Omni and will publish on merge. If the diff matters for your review, reach out to Omni support with the document and branch.
</Step>
</Steps>

## Committing a branch times out

<Steps>
<Step title="What you're seeing" icon="eye">
Committing a branch or opening a pull request fails with this error, and nothing is pushed:


```

**2. Why it happens**

Omni fetches every draft on the branch that requires a pull request and writes them together. A branch with a large number of these drafts can exceed the time limit for writing a single commit.

**3. How to fix it**

Split the work across branches so each branch includes fewer drafts that require a pull request and commit again. If a branch with few drafts still times out, reach out to Omni support.

## Next steps

* [Repository structure](https://docs.omni.co/integrations/git/content/repository-structure.md)
* [Syncing content to git](https://docs.omni.co/integrations/git/content/sync-to-git.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.