Built into the workspace, this visual Git client (also exposed as an API) clones a remote repository over HTTPS into a folder, where you can branch, commit, push, pull and fix conflicts.
Also called formerly Repos, Repos.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Git folders in context, with comparison tables and the common traps.
Terms in this definition
- Workspace
Teams in Power BI and Microsoft Fabric collaborate in this folder-style container, which groups items such as reports, semantic models and lakehouses, controls who can access them and is assigned a capacity.
- Git
A distributed version control system. Anything kept in Git, prompts included, gains a history of authors, timestamps, diffs and tags, and changes can be reverted.
- API
Short for application programming interface: a contract that client code calls programmatically, for example a web API secured with tokens or the Files, Images or Responses APIs.
- Repository
A group of images or artefacts in a container registry that share one name and differ by tag. Names can include slash-separated namespaces, but every repository is handled separately.
- OVER
Gives a T-SQL window function its window: PARTITION BY, ORDER BY and, if wanted, a ROWS or RANGE frame. Rankings and running totals can then be worked out while every row is kept.
- HTTPS
Secure HTTP, wrapped in TLS. VCF products serve their web UIs and REST APIs this way on 443.
- WHERE
Limits a SELECT, UPDATE or DELETE to just the rows meeting a condition. Omit it, and the statement hits every row.
- Real-time streaming semantic model
Covers live-fed push, streaming and PubNub models, plus streaming dashboard tiles. Microsoft now steers people towards Real-Time Intelligence in Fabric, as these are being retired and new ones can only be made until 31 October 2027.
Related terms
- GPG
A tool used to sign Git commits cryptographically; signing commits with GPG isn't available in Azure Databricks Git folders.
- IPYNB
Jupyter's notebook format. Unlike source-format notebooks, notebooks in this format can be created and committed from Git folders with their cell outputs, if you want them.
- Production Git folder
An admin-created Git folder, kept outside user folders, that follows the deployment branch. Only automation updates it, typically a service principal using the Repos API each time a pull request merges.
- Rebase
An action in Git folders that moves your local commits so they sit after the latest commits on the target branch, giving a straight-line history, and then force-pushes the result. Because history is rewritten, it behaves differently from a merge.