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.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Production Git folder in context, with comparison tables and the common traps.
Terms in this definition
- 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.
- Chat message roles
Labels on chat messages: instructions go under system, the person's input under user, the model's previous answers under assistant, and results returned by a called tool under tool (or function).
- Model deployment
Inside a resource, each deployment is a named copy of a Foundry model with its own TPM quota and deployment type. Requests identify the model by this deployment name.
- Service principal
The tenant-local instance of a managed identity or app registration, which users and Azure or directory roles are assigned to. Those from app registrations authenticate with a stored certificate or secret that needs rotating and can be copied, which suits code running outside Azure.
- Git folders
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.
- 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.
- Pull request
In Azure Repos or GitHub, a proposal to merge one branch into another, at which point reviewers and branch policies or protection rules come into play.