Git blame correlation: Identify who introduced the breaking change

[nomadicmehul]

Summary

When the agent traces a root cause to a specific deployment or config change, use git blame / commit history to identify which commit and author introduced the change.

Why This Matters

Knowing WHO made the change helps route the incident to the right person for review. Combined with auto-PR generation, this enables targeted code review.

Acceptance Criteria

• Given a K8s deployment change, find the corresponding git commit
• Map container image tag → git commit SHA (via image label or tag convention)
• Run git blame on changed files to identify the author
• Include in RCA: "Change introduced by [author] in commit [sha] — [message]"
• Respect privacy: this is for routing, not blaming — frame as "best person to review"

Dependencies

• Requires GitHub integration (repo access)
• Works best with image tagging convention (e.g., image tag = git SHA)