Git

In the Ultra Transcenders books

AI-300

Each book explains Git in context, with comparison tables and the common traps.

Terms in this definition

• VCS

  Short for version control system: where the platform's infrastructure code is kept and its pipelines run. Azure DevOps and GitHub are supported by the Azure landing zone accelerator, with a local choice for other systems.

• Image tagging

  An Image Analysis feature producing single-word tags, each with a confidence score, for actions, scenery, objects and living things in an image.

Related terms

• Apache Airflow job

  A code-first Fabric Data Factory item for orchestrating work as Python DAGs on managed Apache Airflow, offering starter or custom pools, autoscaling and syncing DAGs from Git. It succeeds Workflow Orchestration Manager in Azure Data Factory and sits alongside pipelines as their code-based counterpart.

• Azure Repos

  Azure DevOps' version control: Git (and legacy centralised TFVC), guarded by branch permissions and policies. GitHub's counterpart is its repositories.

• Azure Repos for Teams

  GitHub repositories aren't supported, but TFVC and Git repositories can have their events posted into a Teams channel by this app.

• BFG Repo-Cleaner

  An open-source utility that strips files or rewrites text across a Git repository's whole history, and is easier to use than git filter-branch. GitHub's own guidance uses git filter-repo.

• Branch workspace

  Gives a developer an isolated copy of Fabric items, a SQL database for example. Branch out to new workspace creates a new Git branch, links a new workspace to it and fills it with the definitions already committed.

• Configuration template

  Captures the wanted settings of a chosen source vCenter so VCF Operations can compare other vCenter instances with it via policies. Git synchronisation is supported.

• Deployment credentials

  Username and password pairs for local Git and FTP/S on App Service. They use basic authentication and are not Entra identities.

• Feature branch

  A Git branch that lives briefly while one developer builds a change, ending in a pull request. Databricks advises trunk-based development, where main is always kept ready to deploy.