Git与TFS能否兼容使用？TFS管控目录下git init执行异常问题咨询

First, let's address why your git init command isn't generating the .git folder or related files like .gitattributes/.gitignore:
TFS (especially when using server-side workspaces) often enforces file system restrictions that block the creation of hidden system folders (like .git) or may flag Git-specific metadata as "unauthorized" within its managed directories. Even when the system recognizes you ran git init before, TFS's underlying workspace controls might be preventing those files from being created or persisted.

Now to your core question: Can Git and TFS work reliably in the same directory?
The short answer is technically "yes" but strongly not recommended. Here's why you'll run into headaches:

• Conflicting state tracking: TFS uses its own workspace tracking (via files like .vssscc or server-side state) while Git relies on the local .git repository. This leads to constant mismatches—for example, TFS might mark a file as "checked out" while Git sees it as an uncommitted change, or vice versa. You'll spend more time untangling state than doing actual work.
• Metadata clashes: TFS has its own ignore file (tfignore) and metadata files that can conflict with Git's .gitignore/.gitattributes. Worse, TFS might try to track Git's .git folder as a managed file, or block it entirely (which is likely what's happening to you).
• Irreconcilable workflows: Git's distributed model and TFS's centralized (or semi-centralized) model don't play nice together. Committing with Git won't update TFS's server state, and checking in with TFS will mess up Git's commit history. There's no seamless way to sync the two without custom scripts that are prone to breaking.

If You Must Use Both (Not Recommended) #

If you have no other option, try these workarounds:

• Separate the directories: Keep your TFS workspace as a parent folder, then initialize Git in a subdirectory that TFS doesn't track. Or vice versa—use Git for most work, and only sync specific files to TFS when needed (but this defeats the purpose of version control).
• Switch to TFS local workspaces: Server workspaces have stricter restrictions. Switching to a local workspace (in TFS settings) might relax the file system rules enough to let Git create its .git folder.
• Manually create Git files: If git init won't generate .gitignore or .gitattributes, create them manually in the directory. Just be sure to add them to TFS's tfignore so TFS doesn't try to track them.

Final Takeaway #

Save yourself the frustration: Pick one version control system to use for your directory. If you're migrating from TFS to Git, do a full migration instead of trying to run both side-by-side.

内容的提问来源于stack exchange，提问作者MGSeggerman