Through package management to your systems. What kind of files should you store in Git? Source code-not dependenciesĪs your team works with editors and tools to create and update files, you should put these files into Git so your team can enjoy the benefits of Git's workflow.ĭon't commit other types of files, such as DLLs, library files, and other dependencies that aren't created by your team but your code depends on into your repo. If many versions of these files exist in your repo, they will dramatically increase the time to checkout, branch, fetch, and clone your code. If you have large, undiffable files in your repo such as binaries, you will keep a full copy of that file in your repo every time you commit a change to the file.
Git's fast performance comes from its ability to address and switch to all versions of a file from its local storage. Large files that don't compress well and change entirely between versions (such as binaries) present problems when stored in your Git repos. Git is great at keeping the footprint of your source code small because the differences between versions are easily picked out and code is easily compressed. Azure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019 | TFS 2018