---
title: 'Some of You Will "Git" This'
description: Pull requests, diffs, hooks, tests and pipelines - for your production data. Data Controller brings the git workflow to master data management in SAS.
date: '2026-08-13 14:00:00'
author: 'Data Controller'
authorLink: https://www.linkedin.com/showcase/data-controller-for-sas
tags:
  - Announcements
previewImg: './gitflow.png'
---

# Some of You Will "Git" This

If you could make a "pull request" for production data, how might that look?

Perhaps:

- ✅ A [before / after comparison](https://docs.datacontroller.io/dc-userguide/) of the values that had changed
- ✅ [Security](https://docs.datacontroller.io/dcc-security/) (who can submit / approve in each "repo")
- ✅ Only store the changed data (not full copies)
- ✅ A new "diff" when the base table changes
- ✅ Ability to choose [one or more approvers](https://docs.datacontroller.io/dcc-tables/)
- ✅ [HOOK scripts](https://docs.datacontroller.io/dcc-tables/) before / after a commit
- ✅ Tests ([DQ checks](https://docs.datacontroller.io/dcc-validations/)) prior to merge
- ✅ A [pipeline](https://docs.datacontroller.io/dcc-tables/) following a merge
- ✅ [Emails](https://docs.datacontroller.io/emails/) for "status" changes
- ✅ Comments by reviewers
- ✅ Full [history](https://docs.datacontroller.io/dc-userguide/) of changes

Sound familiar? This is exactly how developers have managed *code* for decades - and Data Controller brings the same discipline to *data*. Every edit to a table in SAS® goes through an edit - stage - approve workflow: changes are staged as a diff, checked by validation rules and hook scripts, reviewed and approved by the people you choose, then loaded. The audit trail captures who changed what, when and why - the `git blame` of master data.

If you're ready to "commit" to Data Control, we invite you to "clone" the latest version of [Data Controller for SAS®](https://datacontroller.io) - which has ALL these features - and "push" to your "main" environment for some "master" data management!

<!-- Source LinkedIn post:
Some of you will "git" this..

If you could make a "pull request" for production data, how might that look?

Perhaps:

✅ A before / after comparison of the values that had changed
✅ Security (who can submit / approve in each "repo")
✅ Only store the changed data (not full copies)
✅ A new "diff" when the base table changes
✅ Ability to choose one or more approvers
✅ HOOK scripts before / after a commit
✅ Tests (DQ checks) prior to merge
✅ A pipeline following a merge
✅ Emails for "status" changes
✅ Comments by reviewers
✅ Full history of changes

Sound familiar? This is exactly how developers have managed CODE for decades - and Data Controller brings the same discipline to DATA. 

Every edit to a table in Data Controller for SAS® goes through an edit - stage - approve workflow: changes are staged as a diff, checked by validation rules and hook scripts, reviewed and approved by the people you choose, then loaded. 

The audit trail captures who changed what, when and why - the "git blame" of master data.

If you're ready to "commit" to Data Control, we invite you to "clone" the latest version of Data Controller for SAS - which has ALL these features - and "push" to your "main" environment for some "master" data management!

Link in the comments below 👇

#dataops #mdm #masterdata #dataquality #sas #sasjs #datagovernance
-->

<!-- Image prompt:
A clean, flat-design illustration in the Data Controller brand style showing a database table flowing through a git-style pull-request workflow: rows of a data table on the left passing through a "stage" step shown as a highlighted before/after diff of changed cells, then an approval checkpoint with a tick and reviewer avatars, then merging into a production database cylinder on the right. Git-flavoured touches: a branch line diagram arcing from "staging" branch into "main", small commit dots along the line. Dark navy background, teal/green accents, orange highlights on the changed cells. Minimal text: "stage -> approve -> merge". 16:9 landscape, suitable as a blog/feed cover image.
-->
