📄️ Git as Your Source of Truth
A connected Git repository turns mtdt.io from a deployment tool into a full version-control workflow. Git becomes the baseline your team deploys from, compares against, and pushes changes into — so "what's correct" lives in one place with full history, not scattered across orgs and memories.
📄️ Backing Up Metadata to a Repository
Beyond deployments, mtdt.io can snapshot an org's metadata and push it to a branch as a standalone backup — a complete, source-formatted copy of your configuration, versioned in Git. No deployment required, and no sfdx scripts to maintain.
📄️ Deploying and Pushing to a Repository
When you deploy a change to an org, the same change should land in your repository — otherwise Git quietly falls behind the org. mtdt.io gives you two ways to get a deployed change into the repo, differing only in when it happens.
📄️ Pushing Changes as a Pull Request
Sometimes a change shouldn't land straight on a protected branch. Instead of committing directly, mtdt.io can push a change set to your repository as a pull request — so it goes through normal code review before it's merged.