Git repository and deployed code baseline
Availability: preview
Git configuration provides repository context for investigation and candidate changes. It does not grant automatic merge or deployment authority.
Repository configuration
Section titled “Repository configuration”A project stores the remote URL, SCM provider, https or ssh transport,
credential reference, production branch, and exact deployed commit. Create the
credential separately and reference its server-owned ID; credential reads never
return its value.
Use an immutable commit SHA for deployedCommit. A branch name alone is not an
incident baseline.
Baseline capture
Section titled “Baseline capture”When an incident generation starts, Mendry captures the project’s configured deployed commit. Reopening a recovered incident creates a new generation and reads the current configured commit again. Existing generation evidence and reviews keep their original baseline.
Investigation boundary
Section titled “Investigation boundary”The trusted Git adapter may clone/fetch the configured remote, resolve the exact baseline, inspect bounded history/diffs, and prepare candidate changes in an isolated workspace. Repository URLs and credentials come from project configuration, never model output.
A candidate branch, patch, validation result, or publication record is review evidence. People still authorize change-request creation, merge, deployment, and rollback.
Verified against
Section titled “Verified against”backend/README.md