Team Foundation Version Control, a centralised system in Azure Repos that keeps history on the server and branches by path. No new features are planned, all new work goes into Git, and YAML pipelines can't use it.
Also called Team Foundation Version Control.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains TFVC in context, with comparison tables and the common traps.
Terms in this definition
- 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).
- Azure Repos
Azure DevOps' version control: Git (and legacy centralised TFVC), guarded by branch permissions and policies. GitHub's counterpart is its repositories.
- PATH
Parent-child hierarchies in DAX rely on this function. For each row it builds one delimited text value listing the IDs of the row's ancestors, top level first and ending with the row's own ID, which PATHITEM, PATHLENGTH and friends can then pick apart.
- Document Intelligence add-on capabilities
Extra Document Intelligence options switched on with the features query parameter: barcodes, formulas, keyValuePairs, languages, ocrHighResolution, queryFields and styleFont.
- ALL
A DAX function that ignores any filters and gives back every row of a table or every value of the named columns. Used within CALCULATE, it works as a modifier that clears filters, although REMOVEFILTERS states that intent more clearly where it is available.
- 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.
- YAML
A data format designed to be easy for people to read, used for Container Apps definitions, ACR multi-step tasks and Kubernetes manifests.
Related terms
- 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.