Troubleshooting content in git

</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: