Supported asset types in Git folders

Git folders support version control for specific Databricks asset types. When an asset type is supported in Git folders, you can commit it to a remote Git repository, track changes over time, and collaborate with other users through version control.

The following table describes the supported asset types and their requirements:

Asset type	Details
File	Serialized data such as libraries, binaries, code, or images. See What are workspace files?.
Notebook	Notebook file formats supported by Databricks. Git folders identify notebooks by file extension (.ipynb) or by a special marker in the file content, such as a # Databricks notebook source comment at the beginning of .py files. Notebooks aren't serialized like other file types. See Notebook formats.
Folder	A logical grouping of files that appears as a folder in the Databricks workspace and CLI.
Query (Public Preview)	Databricks SQL queries saved as .dbquery.ipynb files. Requires the new SQL editor. You can't commit queries created with the legacy SQL editor.
Dashboard (Public Preview)	Databricks AI/BI dashboard drafts saved as .lvdash.json files. Publishing and scheduling configurations aren't tracked.
Alert (Public Preview)	Alerts saved as .dbalert.json files. Git folders track alert schedules, but cloned alerts start paused and you must resume them manually.

File naming requirements

When you work with assets in Git folders, follow these file naming rules:

• Unique notebook names: A folder can't contain a notebook with the same name as another notebook, file, or folder, even with different extensions. For example, a source-format notebook test1.py and a notebook in .ipynb format can't coexist because both serialize to test1.
• No forward slashes: File names can't contain the / character. For example, i/o.py isn't a valid file name.

If you violate these rules, Git operations fail with an "Error fetching Git status" message. To resolve the error, rename the conflicting files in your repository.

Unsupported asset types

The following asset types aren't supported in Git folders:

• Legacy alerts
• Legacy dashboards
• MLflow experiments
• Genie spaces

note

You can move unsupported assets into a Git folder, but you can't commit changes to the remote repository.

Notebook formats

For information about notebook formats for source control, see Notebook formats.