Introduction to Git Sync on Grafana Labs

Git Sync Key concepts

Fri, 03 Apr 2026 19:43:06 +0000

Git Sync key concepts

Caution
Git Sync is available in public preview for Grafana Cloud, and is an experimental feature 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 for more information. Contact Grafana for support or to report any issues you encounter and help us improve this feature.

Key Git Sync components

Before you start using Git Sync, understand how the key Git Sync components relate:

Grafana instance

A Grafana instance is a running Grafana server. Multiple instances can:

Connect to the same Git repository using different Repository configurations.
Sync from different branches of the same repository.
Sync from different paths within the same repository.
Sync from different repositories.

Git repository

A Git repository is the external storage you want to sync your Grafana instance with. You can organize your Git repository in several ways:

Single branch, multiple paths: Use different directories for different purposes. For example, dev/, prod/, or team-a/.
Multiple branches: Use different branches for different environments or teams. For example, main, develop, or team-a.
Multiple repositories: Use separate repositories for different teams or environments.

Flexible configuration for your Git Sync repositories

Git Sync repositories support different combinations of repository URL, branch, and path:

Different Git repositories: Each environment or team can use its own repository.
- Instance A: repository: your-org/grafana-prod.
- Instance B: repository: your-org/grafana-dev.
Different branches: Use separate branches within the same repository.
- Instance A: repository: your-org/grafana-manifests, branch: main.
- Instance B: repository: your-org/grafana-manifests, branch: develop.
Different paths: Use different directory paths within the same repository.
- Instance A: repository: your-org/grafana-manifests, branch: main, path: production/.
- Instance B: repository: your-org/grafana-manifests, branch: main, path: development/.
Any combination: Mix and match based on your workflow requirements.

Git Sync repository resource

A repository resource is a Grafana configuration object that defines the connection between a group of repositories and your Grafana instance via Git Sync.

Which Git repository to sync with your Grafana instance.
Which branch to use.
Which directory path to synchronize.
Sync behavior and workflows.

Each repository resource creates bidirectional synchronization between a Grafana instance and a specific location in Git.

Git Sync connection resource

A connection is the authentication setup between Grafana and an external Git provider, required when you’re not using a Personal Access Token or a static token to authenticate. Use it to authorize access to your external repositories, and to generate or refresh the credentials for Git Sync. A single connection can be reused across multiple repositories.

For example, if you’re using GitHub App to authenticate, the connection represents the app installation. Grafana uses this connection to authenticate with GitHub, create access tokens, and authorize repository access on your behalf.

The connection resource includes:

The external provider configuration: The authentication mechanism Grafana uses to communicate with the Git provider (for example, a GitHub App).
The provider authorization or installation: The authorized entity that allows Grafana to request tokens from the provider.
Repository access scope: The set of repositories that the connection (and therefore, Grafana) is authorized to access in the Git provider.

How does Git Sync behave?

Git Sync is bidirectional, and syncs a repository resource with your Grafana instance. You can modify provisioned resources both from the Grafana UI or from the synced GitHub repository, and changes will be reflected in both places:

Grafana monitors the specified Git location (repository, branch, and path).
Grafana creates a folder in Dashboards (typically named after the repository).
Grafana creates dashboards from dashboard JSON files in Git within this folder.
Grafana commits dashboard changes made in the UI back to Git.
Grafana pulls dashboard changes made in Git and updates dashboards in the UI.
Synchronization occurs at regular intervals (configurable), or instantly if you use webhooks.

You can find the provisioned dashboards organized in folders under Dashboards.

Git Sync states

Your Grafana instance can be in one of the following Git Sync states:

Unprovisioned: None of the instance’s resources are being managed by Git Sync.
Partially provisioned: Some of the resources are controlled by Git Sync.
Fully provisioned: All supported resource types are managed by Git Sync. Unsupported resources are not managed.

Example: Relationship between repository, branch, and path

Here’s an example showing how the repository, branch, and path concepts work together:

Configuration:

Repository: your-org/grafana-manifests
Branch: main
Path: team-platform/grafana/

In Git (on branch main):

your-org/grafana-manifests/
├── .git/
├── README.md
├── team-platform/
│   └── grafana/
│       ├── cpu-metrics.json       ← Synced
│       ├── memory-usage.json      ← Synced
│       └── disk-io.json           ← Synced
├── team-data/
│   └── grafana/
│       └── pipeline-stats.json    ← Not synced (different path)
└── other-files.txt                ← Not synced (outside path)

In the Grafana Dashboards view:

Dashboards
└── 📁 grafana-manifests/
    ├── CPU Metrics Dashboard
    ├── Memory Usage Dashboard
    └── Disk I/O Dashboard

Key takeaways:

Grafana only synchronizes files within the specified path (team-platform/grafana/).
Grafana ignores files in other paths or at the repository root.
The folder name in Grafana comes from the repository name.
Dashboard titles come from the JSON file content, not the filename.

Usage and performance limitations

Fri, 03 Apr 2026 19:43:06 +0000

Usage and performance limitations

Caution
Git Sync is available in public preview for Grafana Cloud, and is an experimental feature 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 for more information. Contact Grafana for support or to report any issues you encounter and help us improve this feature.

Performance considerations

When Git Sync is enabled, the database load might increase, especially if your Grafana instance has many folders and nested folders. Evaluate the performance impact, if any, in a non-production environment.

Usage tiers

The following Git Sync per-tier limits apply:

Tier	Cloud - Free	Cloud - Other	On-prem OSS	On-prem Enterprise
Amount of repositories	1	10	10	10
Amount of synced resources per repository	20	Grafana limit	No limit	No limit

Compatible Git providers

Git Sync is available for any Git provider through a Pure Git repository type, and has specific enhanced integrations for GitHub, GitLab and Bitbucket.

Provider	Available in	Authentication
Pure Git	Cloud, OSS, Enterprise	Personal Access Token
GitHub	Cloud, OSS, Enterprise	Personal Access Token or GitHub App
GitLab	Cloud, Enterprise	Personal Access Token
Bitbucket	Cloud, Enterprise	API token with scopes

Note that Pure Git, GitLab and Bitbucket are supported in Grafana v12.4.x only. Refer to Enable required feature toggles to set them up.

The Pure Git repository type

The Pure Git repository type uses the standard Git over HTTP protocol, with no provider-specific logic. Pure Git delivers the core Git Sync workflow: your repository is the source of truth, you may edit dashboards in the UI, and Grafana stays in sync.

However, Pure Git doesn’t include any features that require provider APIs, such as webhook-driven instant sync, automated PR comments, or deep links to source files.

Enhanced integrations: GitHub, GitLab, Bitbucket

If your Git provider is GitHub, GitLab, or Bitbucket, use the enhanced integration. Enhanced integrations understand the platform you’re using, allowing workflows that feel native: automated pull request comments with dashboard previews, instant webhook-based sync, or direct navigation from Grafana to source files in your provider’s UI.

The GitHub enhanced integration is the most feature-complete experience today. It enables richer pull request workflows, deeper linking between Grafana and GitHub, and tighter integration into review processes. It is available in Grafana OSS, Enterprise, and Cloud.

The GitLab and Bitbucket integrations have limited functionality for the moment, and are only available in Grafana Enterprise and Grafana Cloud. Expect continued improvements around pull request workflows, linking, and sync behavior in upcoming releases.

Resource support and compatibility

Git Sync only supports dashboards and folders. Alerts, data sources, panels and other resources are not supported yet.

If you’re a Grafana Cloud user, you can check the Grafana roadmap portal to learn about future improvements.

Resource compatibility

If you’re using Git Sync in Grafana OSS or Grafana Enterprise, some supported resources might be in an incompatible data format. If this happens, syncing will be blocked. Compatibility issues will be fixed with an upcoming migration tool.

A resource can be:

Is the resource?	Compatible	Incompatible
Supported	The resource can be managed with Git Sync.	The resource is supported but has compatibility issues. It cannot be managed with Git Sync.
Unsupported	The resource is not supported and cannot be managed with Git Sync.	Not applicable.

Known limitations

Synced resources

You can only sync dashboards and folders. Refer to Supported resources for more information.
If you’re using Git Sync in Grafana OSS and Grafana Enterprise, some resources might be in an incompatible data format and won’t be synced.
Full-instance sync is not available in Grafana Cloud and is experimental in Grafana OSS and Grafana Enterprise.
When migrating to full instance sync, during the synchronization process your resources will be temporarily unavailable. No one will be able to create, edit, or delete resources during this process.
If you want to manage existing resources with Git Sync, you need to save them as JSON files and commit them to the synced repository. Use grafanactl or open a PR to import, copy, move, or save a dashboard. Refer to Export non-provisioned resources from Grafana for more details.
Restoring resources from the UI is currently not possible. As an alternative, you can restore dashboards directly in your GitHub repository by raising a PR, and they will be updated in Grafana.

Permission management

You cannot modify the permissions of a provisioned folder after you’ve synced it.

The default permissions are:

Admin = Admin
Editor = Editor
Viewer = Viewer.

Refer to Roles and permissions for more information.

Set up Git Sync

Fri, 03 Apr 2026 19:43:06 +0000

Set up Git Sync

Caution
Git Sync is available in public preview for Grafana Cloud, and is an experimental feature 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 for more information. Contact Grafana for support or to report any issues you encounter and help us improve this feature.

To set up Git Sync and synchronize your Grafana dashboards and folders with a GitHub repository, follow these steps:

Read Before you begin carefully
Set up Git Sync using the UI, as code, or with Terraform
After setup, verify your dashboards
Optionally, you can also extend Git Sync with webhooks and image rendering

Set up Git Sync using the UI

To set up Git Sync from the Grafana UI, follow these steps:

Log in to your Grafana server with an account that has the Grafana Admin flag set.
Select Administration > General > Provisioning in the left-side menu to access the Git Sync configuration screen. If you already have an active Git Sync connection, go to the Get started tab.
Select your provider to start a new Git Sync setup: GitHub, GitLab, Bitbucket, or Pure Git.
Configure the provisioning repository.
Choose what content to sync with Grafana.
Synchronize with external storage.
Choose additional settings.

Select your provider

Git Sync is available for any Git provider through a Pure Git repository type, and has specific enhanced integrations for GitHub, GitLab and Bitbucket. Refer to Compatible providers for more details.

Alternatively, on-prem file provisioning in Grafana lets you include resources, including folders and dashboard JSON files, that are stored in a local file system. Refer to Provision resources on-prem for more details.

Select any of the following options to proceed:

Configure with GitHub

If you want to configure Git Sync for GitHub, you can connect using a Personal Access Token or with GitHub App.

Connect with a GitHub Personal Access Token

If you want to configure Git Sync for GitHub and authenticate with a Personal Access Token, sign in to GitHub and create a new fine-grained personal access token with these permissions:

Contents: Read and write permission
Metadata: Read-only permission
Pull requests: Read and write permission
Webhooks: Read and write permission

Refer to Managing your personal access tokens for instructions.

Return to Grafana and fill in the following fields:

Paste your GitHub personal access token into Enter your access token.
Paste the Repository URL for your GitHub repository into the text box.

Select Configure repository to set up your provisioning folder.

Connect with GitHub App

Note
Refer to Create a GitHub App for instructions on how to create a GitHub App.

If you want to configure Git Sync for GitHub and authenticate with GitHub App:

If you already have an existing GitHub App connected:
1. Select Choose an existing app.
2. Click on the existing connection you want to use, and click on Configure repository to proceed.
3. Paste the Repository URL for your GitHub repository into the text box.
If you want to connect using a new GitHub App:
1. Select Connect to a new app.
2. Type in the following fields:
  - The ID of the GitHub App you want to use
  - The GitHub Installation ID
  - The Private Key
3. Click on Configure repository to proceed.
4. Paste the Repository URL for your GitHub repository into the text box.

Note that your GitHub App must have the following permissions:

Contents: Read and write permission
Metadata: Read-only permission
Pull requests: Read and write permission
Webhooks: Read and write permission

Select Configure repository to set up your provisioning folder.

Configure with GitLab

If you want to configure Git Sync for GitLab, you need a GitLab Personal Access Token. To create one, sign in to GitLab and create a token with these permissions:

Repository: Read and write permission
User: Read only permission
API: Read and write permission

If you’re using a token from a service account, you need to add the service account to the GitLab project as a member to avoid authentication issues.

After creating the token, return to Grafana and fill in the following fields:

Paste the token into the Project Access Token text box.
Paste the Repository URL for your GitLab repository into the text box.

Select Configure repository to set up your provisioning folder.

Configure with Bitbucket

If you want to configure Git Sync for Bitbucket, you need a Bitbucket API token with scopes. To create one, sign in to Bitbucket and create an API token with these permissions:

Repositories: Read and write permission
Pull requests: Read and write permission
Webhooks: Read and write permission

Return to Grafana and fill in the following fields:

Paste the token into the API Token text box.
Paste the Repository URL for your GitLab repository into the text box.

Select Configure repository to set up your provisioning folder.

Configure with Pure Git

If you’re using another Git provider, you need to use the Pure Git option to configure your connection with a Personal Access Token:

Paste the access token or password of the Git repository you want to sync in Access Token.
Enter a Username. Git Sync will use this name to access the Git repository.
Paste the Repository URL of your Git repository into the text box.

Select Configure repository to set up your provisioning folder.

Configure the provisioning repository

After configuring your connection authentication, continue to enter the details of the repository you want to use for provisioning:

Enter a Branch to use for provisioning. The default value is main.
Optionally, you can add a Path to a subdirectory where your dashboards are stored.

Select Choose what to synchronize to have the connection to your repository verified and continue setup.

Choose what to synchronize

On this screen, you will sync the external resources you specified in the previous step with your Grafana instance. These provisioned resources will be stored in a new folder in Grafana without affecting the rest of your instance.

To set up synchronization:

Select the external storage you want to sync with your Grafana instance. The UI provides information about the available resources you can sync.
Enter a Display name for your repository connection. All the synced resources from this Git Sync connection will appear under the this name in the Grafana UI.
Click Synchronize with external storage to continue.
You can repeat this process for up to 10 connections.

Note
Optionally, you can export any unmanaged resources into the provisioned folder. See how in Synchronize with external storage.

Select Choose additional settings to continue setup.

Synchronize with external storage

In this screen:

Review the known limitations before proceeding.
Check the Migrate existing resources box to migrate your unmanaged dashboards to the provisioned folder. If you select this option, all future updates are automatically saved to the synced Git repository and provisioned back to the instance.
Click Begin synchronization to create the Git Sync connection.

After the process is completed, you will see a summary of the synced resources.

Click Choose additional settings for the final configuration steps.

Choose additional settings

In this last step, you can configure the Sync interval (seconds) to indicate how often you want your Grafana instance to pull updates from GitHub. The default value is 300 seconds in Grafana Cloud, and 60 seconds in Grafana OSS/Enterprise.

You can also select these optional settings:

Check Read only to ensure resources can’t be modified in Grafana.
Check Enable pull request option when saving to choose whether to open a pull request when saving changes. If the repository does not allow direct changes to the main branch, a pull request may still be required.
Check Enable push to configured branch to allow direct commits to the configured branch.

Select Finish to complete the setup.

Verify your dashboards in Grafana

To verify that your dashboards are available at the location that you specified, go to Dashboards. The name of the dashboard is listed in the Name column.

Now that your dashboards have been synced from a repository, you can customize the name, change the branch, and create a pull request (PR) for it. Refer to Manage provisioned repositories with Git Sync for more information.

Update or delete your synced resources

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

Log in to your Grafana server with an account that has the Grafana Admin flag set.
Select Administration > General > Provisioning.
Go to the Repositories tab, and locate the repository you want to modify.
Select Settings to access the Configure repository screen:

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.

Next steps

You’ve successfully set up Git Sync to manage your Grafana dashboards through version control. Your dashboards are now synchronized with a GitHub repository, enabling collaborative development and change tracking.

To learn more about using Git Sync refer to the following documents:

Add non-provisioned resources from Grafana

Fri, 03 Apr 2026 19:43:06 +0000

Export non-provisioned resources from Grafana

Caution
Git Sync is available in public preview for Grafana Cloud, and is an experimental feature 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 for more information. Contact Grafana for support or to report any issues you encounter and help us improve this feature.

Git Sync is under development, and traditional operations like moving or copying a dashboard to a provisioned folder are not fully supported for resources already existing in Grafana. Git Sync doesn’t offer any built-in functionality to easily export resources from Grafana in bulk. However, the following options are available:

Add an existing dashboard from the Grafana UI

You can save a copy of dashboard directly from the Grafana UI to your provisioned folder.

To do so, follow these steps:

Make sure the dashboard is in Editable mode.
Select Save or Save as from the top-right corner.
In the menu:
- Target folder: Select the provisioned folder from your Grafana UI where you want to save the dashboard in.
- Branch: Type in the name of the branch of the provisioned repository you want to work in, or create a new branch. Committing directly to main is not supported.
- Folder: Type in the folder in your sync repository, if any.
- Fill in the rest of the fields accordingly.
Click Save.
In your synced GitHub repository, merge the branch with the dashboard you want to sync.

Add a dashboard with Grafana CLI

You can also export an existing dashboard with the Grafana CLI. Use the CLI to download the resources you want to sync from Grafana, and then commit and push those files to your provisioned Git repository. Git Sync will then detect the commit, and synchronize with Grafana.

To do so, follow these steps:

Set up the grafanactl context to point to your instance as documented in Defining contexts.
Pull the resources you want to sync from the instance to your local repository:

grafanactl resources pull dashboards --path <REPO_PATH>

Next, commit and push the resources to your Git repository:

git add <DASHBOARDS_PATH>
git commit -m "Add dashboards from Grafana"
git push

Where:

<GIT_REPO>: The path to the repository synced with Git Sync
<DASHBOARDS_PATH>: The path where the dashboards you want to export are located. The dashboards path must be under the repository

See more at Manage resources with Grafana CLI.

Add a dashboard via JSON export

To add an existing dashboard to Git Sync via JSON export, you need to:

Export the dashboard as JSON.
Convert it to the Custom Resource Definition (CRD) format required by the Grafana App Platform.
Commit the converted file to your Git repository.

Required JSON format

To export a dashboard as a JSON file it must follow this CRD structure:

{
  'apiVersion': 'dashboard.grafana.app/v1beta1',
  'kind': 'Dashboard',
  'metadata': { 'name': 'dcf2lve9akj8xsd' },
  'spec': { /* Original dashboard JSON goes here */ },
}

The structure includes:

apiVersion: Specifies the API version (currently v1beta1)
kind: Identifies the resource type (Dashboard)
metadata: Contains the dashboard identifier uid. You can find the identifier in the dahsboard’s URL or in the exported JSON
spec: Wraps your original dashboard JSON

Work with Git-managed dashboards

After you’ve saved a dashboard in Git, it’ll be synchronized automatically, and you’ll be able to work with it as any other provisioned resource. Refer to Work with provisioned dashboards for more information.

Work with provisioned repositories in Git Sync

Fri, 03 Apr 2026 19:43:06 +0000

Work with provisioned repositories in Git Sync

Caution
Git Sync is available in public preview for Grafana Cloud, and is an experimental feature 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 for more information. Contact Grafana 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:

Log in to your Grafana server with an account that has the Grafana Admin flag set.
Select Administration > General > Provisioning in the left-side menu to access the Git Sync configuration screen.
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 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 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.

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:

Log in to your Grafana server with an account that has the Grafana Admin flag set.
Select Administration > General > Provisioning.
Go to the Repositories tab, and locate the repository you want to modify.
Select Settings to access the Configure repository screen:

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.

Work with provisioned dashboards in Git Sync

Fri, 03 Apr 2026 19:43:06 +0000

Work with provisioned dashboards in Git Sync

Caution
Git Sync is available in public preview for Grafana Cloud, and is an experimental feature 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 for more information. Contact Grafana for support or to report any issues you encounter and help us improve this feature.

Using provisioning, you can choose to store your dashboard JSON files in either GitHub repositories using Git Sync or a local path, and manage them through the Grafana interface. Dashboards and folders synchronized using Git Sync or a local path are referred to as provisioned resources. For more information, refer to the Dashboards documentation.

Git Sync is the recommended method for provisioning your dashboards. You can synchronize any new dashboards and changes to existing dashboards to your configured GitHub repository. If you push a change in the repository, those changes are mirrored in your Grafana instance. Refer to Set up file provisioning to learn more about the version of local file provisioning in Grafana 12.

Manage dashboards provisioned with Git Sync

Using Git Sync, you can manage your dashboards in the UI and synchronize them with a GitHub repository. Refer to How it works for more details.

Dashboards saved in your repository or local folder configured with Git Sync appear in a provisioned folder in Grafana.
Any dashboard folders saved with Git Sync have a Provisioned label in the UI.
To save any changes to provisioned resources, open a pull request or commit directly to an existing branch, such as the main branch.
- Use pull requests to review changes to dashboards.
- Preview the changes before merging.

To learn more about Git, refer to Getting Started - About Version Control of the Pro Git book in the official Git documentation.

Create a new dashboard

Note
If you want to add an existing dashboard to your provisioned resources, refer to Export non-provisioned resources from Grafana.

You have two options for creating new dashboards or folders in Git Sync:

Create them directly within Git Sync-managed folders in the Grafana UI
Add them by committing JSON files to your Git repository

When you create a new dashboard in a provisioned folder associated with a GitHub repository, you follow the same process you use for any new dashboard. Refer to Create a dashboard for more information.

After you create the dashboard, follow these steps:

Select Save to preserve the new dashboard.
Enter a title for the dashboard and a description.
Select the provisioned folder from the Folder drop-down list.
In Path, provide the path for your repository, ending in a JSON or YAML file.
For Workflow, select Push to main to make a Git commit directly to the repository or Push to a new branch to create a pull request.
- Branch: Specify the branch name in GitHub (for example, main). This option only appears if you select Push to a new branch.
Select Save.

Edit dashboards

When you edit a provisioned resource, you’re prompted to save or discard those changes. Saving changes requires opening a pull request in your GitHub repository.

To save dashboard changes:

Select Edit to update a provisioned dashboard. Make your desired changes.
Click Save dashboard.
On the Provisioned dashboard panel, choose the options you want to use:
- Update default refresh value: Check this box to make the current refresh the new default
- Update default variable values: Check this box to make the current values the new default
- Path: Provide the path for your repository, ending in a JSON or YAML file
- Workflow: Select Push to main to make a Git commit directly to the repository or Push to a new branch to create a pull request
- Branch: Specify the branch name in GitHub (for example, main). This option only appears if you select Push to a new branch
- Comment: Add a comment describing your changes
Optional: Select the Changes tab to view the differences between the updates you made and the original resource.
Select Save.
If you chose Push to a new branch, select Open a pull request in GitHub to open a new PR to your repository. GitHub opens with your dashboard’s code as the contents of the PR.
Follow your usual GitHub workflow to save and merge the PR to your repository.

Remove dashboards

You can remove a provisioned dashboard by deleting the dashboard from the repository. The Grafana UI updates when the changes from the GitHub repository sync.

To restore a deleted dashboard, raise a PR directly in your GitHub repository. Restoring resources from the UI isn’t possible at the moment.

Best practices

Follow these recommendations when working with provisioned dashboards:

Use GitHub pull requests for changes: Maintain review processes for dashboard modifications
Provide clear commit messages: Describe your changes to help with tracking and collaboration
Regularly sync your repository: Keep Grafana up to date with the latest changes
Review the Events tab: Monitor sync status to ensure changes are applied correctly

Git Sync deployment scenarios

Fri, 03 Apr 2026 19:43:06 +0000

Git Sync deployment scenarios

Caution
Git Sync is under development. It reflects Grafana’s approach to Observability as Code and might include limitations or breaking changes. For current status and known issues, refer to the Git Sync introduction.

This guide shows practical deployment scenarios for Grafana’s Git Sync. Learn how to configure bidirectional synchronization between Grafana and Git repositories for teams, environments, and regions.

Learn more

Refer to the following documents to learn more: