---
title: "Work with provisioned repositories in Git Sync | Grafana documentation"
description: "Instructions for working with Git Sync to perform common tasks, such as saving dashboards to GitHub and synchronizing changes with Grafana."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

# Work with provisioned repositories in Git Sync

> Caution
> 
> Git Sync is available in [public preview](/docs/release-life-cycle/) for Grafana Cloud, and is an [experimental feature](/docs/release-life-cycle/) in Grafana v12 for open source and Enterprise editions. Documentation and support is available **based on the different tiers** but might be limited to enablement, configuration, and some troubleshooting. No SLAs are provided.
> 
> **Git Sync is under development.** Refer to [Usage and performance limitations](/docs/grafana/v12.4/as-code/observability-as-code/git-sync/usage-limits/) for more information. [Contact Grafana](/help/) for support or to report any issues you encounter and help us improve this feature.

After you have synced your resources, Git Sync creates a dashboard that provides a summary of resources, health, pull status, webhook, sync jobs, resources, and files. To access it, follow these steps:

1. Log in to your Grafana server with an account that has the Grafana Admin flag set.
2. Select **Administration &gt; General &gt; Provisioning** in the left-side menu to access the Git Sync configuration screen.
3. Go to the **Repositories** tab, and locate the repository you want to work with. You can either view the current status of the sync, carry out pulls, or update your settings.

Refer to [Work with provisioned dashboards](/docs/grafana/v12.4/as-code/observability-as-code/git-sync/provisioned-dashboards/) for more information about working with provisioned files.

## View the current status of synchronization

Use the **View** section to see detailed information about the current status of your sync and [troubleshoot](#troubleshoot-synchronization) possible issues:

- The **Overview** tab contains information about the health of your repository’s connection with Grafana, configuration options such as webhooks, or information on Git processes.
- The **Resources** tab lists the provisioned resources of the connection.

### Troubleshoot synchronization

> Caution
> 
> Before you proceed to troubleshoot, understand the [Usage and performance known limitations](/docs/grafana/v12.4/as-code/observability-as-code/git-sync/usage-limits/).

Monitor the **View** status page for synchronization issues and status updates. Common events include:

- Sync started
- Sync completed
- Sync failed (with error details)
- Sync issues

**Dashboard sync errors**

- If dashboards are not syncing, check if the repository URL is correct and accessible from the Grafana instance.
- Ensure that the configured repository branch exists and is correctly referenced.
- Check for conflicts in the repository that may prevent syncing.

**Dashboard import errors**

- Validate the JSON format of the dashboard files before importing.
- If the import fails, check Grafana logs for error messages and troubleshoot accordingly.

## Synchronize changes

To sync resources between the provisioned repositories and your Grafana instance, click **Pull** under the repository you want to sync, and wait for the synchronization process to complete.

Existing dashboards with the same `uid` are overwritten.

## Update or delete your settings

To update or delete your repository configuration after you’ve completed setup:

1. Log in to your Grafana server with an account that has the Grafana Admin flag set.
2. Select **Administration &gt; General &gt; Provisioning**.
3. Go to the **Repositories** tab, and locate the repository you want to modify.
4. Select **Settings** to access the **Configure repository** screen:

<!--THE END-->

- To modify your configuration, update any of the settings and select **Save**.
- To delete the repository, click **Delete**. You can either keep the synced resources or delete them.
