如何用C#编程连接DevOps未初始化Git仓库并推送本地项目

Got it, let's walk through how to programmatically connect your local project to that auto-generated DevOps Git repo and push all your code up using C#. The go-to library for Git operations in .NET is LibGit2Sharp—it's robust and handles all the heavy lifting for us.

Prerequisites #

• First, install the LibGit2Sharp NuGet package in your project:

  # Using .NET CLI
  dotnet add package LibGit2Sharp
  
  # Or using Package Manager Console
  Install-Package LibGit2Sharp
  

• Generate a Personal Access Token (PAT) in your DevOps account with permissions to read/write to the target repository (make sure to save it somewhere secure—you'll need it for authentication).

Step-by-Step C# Implementation #

Here's a complete method that handles initializing the local repo (if needed), linking to the DevOps remote, staging commits, and pushing:

using LibGit2Sharp;
using System;
using System.Linq;

public class GitDevOpsHelper
{
    public void PushLocalProjectToDevOps(string localProjectPath, string devOpsRepoUrl, string devOpsUsername, string pat)
    {
        // 1. Initialize local Git repo if it doesn't exist
        if (!Repository.IsValid(localProjectPath))
        {
            Repository.Init(localProjectPath);
            Console.WriteLine("✅ Initialized new local Git repository");
        }

        // 2. Open the local repository
        using var repo = new Repository(localProjectPath);

        // 3. Add/update the 'origin' remote pointing to DevOps
        const string remoteName = "origin";
        var existingRemote = repo.Network.Remotes.FirstOrDefault(r => r.Name == remoteName);
        
        if (existingRemote == null)
        {
            repo.Network.Remotes.Add(remoteName, devOpsRepoUrl);
            Console.WriteLine($"✅ Added remote '{remoteName}' -> {devOpsRepoUrl}");
        }
        else if (existingRemote.Url != devOpsRepoUrl)
        {
            repo.Network.Remotes.Update(existingRemote, r => r.Url = devOpsRepoUrl);
            Console.WriteLine($"✅ Updated remote '{remoteName}' to point to {devOpsRepoUrl}");
        }

        // 4. Stage all untracked/modified files
        var repoStatus = repo.RetrieveStatus();
        if (repoStatus.IsDirty)
        {
            Commands.Stage(repo, "*");
            Console.WriteLine("✅ Staged all local changes");
        }

        // 5. Commit changes (handles first commit and subsequent updates)
        bool needsCommit = repoStatus.IsDirty || repo.Head.Tip == null;
        if (needsCommit)
        {
            var signature = new Signature(devOpsUsername, $"{devOpsUsername}@yourorg.com", DateTimeOffset.Now);
            repo.Commit("Initial project push from C# code", signature, signature);
            Console.WriteLine("✅ Committed changes locally");
        }

        // 6. Configure authentication with DevOps PAT
        var credentials = new UsernamePasswordCredentials
        {
            Username = devOpsUsername,
            Password = pat
        };

        var pushOptions = new PushOptions
        {
            CredentialsProvider = (_, __, ___) => credentials
        };

        // 7. Push to the DevOps remote (adjust branch name if your default is 'master')
        try
        {
            var targetBranch = repo.Branches["main"];
            repo.Network.Push(targetBranch, pushOptions);
            Console.WriteLine("🎉 Successfully pushed local project to DevOps repository!");
        }
        catch (LibGit2SharpException ex)
        {
            Console.WriteLine($"❌ Push failed: {ex.Message}");
            // Add custom error handling here (e.g., handle branch conflicts, permission issues)
        }
    }
}

Key Notes #

• Replace Placeholders: Make sure to substitute localProjectPath, devOpsRepoUrl, devOpsUsername, and pat with your actual values.
• Default Branch: DevOps uses main as the default branch for new repos, but if your repo uses master, update the branch name in the push step.
• PAT Permissions: Ensure your PAT has the Code (Read & Write) scope in DevOps—otherwise, you'll get authentication errors.
• Error Handling: Extend the catch block to handle specific scenarios like network issues, stale branches, or permission denials.

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