Azure Kudu能否将构建时修改的文件提交推送回Git？

Great question! Azure Kudu doesn’t have a native one-click feature for this exact workflow, but you can absolutely build this functionality using custom deployment scripting. Here’s a practical, step-by-step breakdown to make it work:

• Leverage Kudu’s custom deployment hooks
  Kudu lets you inject custom logic into the build/deployment pipeline via scripts like deploy.cmd (batch) or deploy.ps1 (PowerShell), or by hooking into post-build stages in your project config. This is where you’ll add the Git commit/push logic.

• Set up secure Git authentication
  To push changes back to your repo, you’ll need a Personal Access Token (PAT) with repo write permissions. Store this PAT in your Azure App Service’s Application Settings (under Configuration > Application Settings) — never hardcode it in scripts for security.

  In your script, configure Git’s user identity and update the remote URL to use the PAT:

  # PowerShell example
  git config --global user.name "Kudu Auto-Deploy Bot"
  git config --global user.email "kudu-bot@yourdomain.com"
  $pat = $env:YOUR_PAT_SETTING_NAME
  git remote set-url origin https://$pat@github.com/your-username/your-repo.git
  

  For batch scripts:

  @echo off
  git config --global user.name "Kudu Auto-Deploy Bot"
  git config --global user.email "kudu-bot@yourdomain.com"
  set pat=%APPSETTING_YOUR_PAT_SETTING_NAME%
  git remote set-url origin https://%pat%@github.com/your-username/your-repo.git
  

• Commit and push the modified file
  Add logic to check if your target file was changed, then commit and push it. Here’s a PowerShell snippet to handle this:

  $targetFile = "path/to/your/specific-file.ext"
  # Check if the file has uncommitted changes
  if (git status --porcelain | Select-String -Pattern $targetFile) {
      git add $targetFile
      git commit -m "Auto-update: $targetFile modified during Kudu build"
      git push origin main # Replace with your target branch name
  }
  

• Critical safeguards to avoid headaches

  • Prevent infinite build loops: Pushing the file might trigger another Kudu build. Fix this by adding a condition in your repo’s build triggers to skip builds when the commit message matches your auto-update pattern (e.g., "Auto-update:").
  • Limit PAT permissions: Give the PAT only the minimum access it needs (repo write is enough — no admin rights required).
  • Handle edge cases: Add checks for empty commits or merge conflicts to avoid script failures breaking your deployment.

That’s all you need! With these steps, you can automate committing and pushing your modified file back to Git directly from the Kudu build process.

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