dc/datacontroller.io
6
1
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

fix: links
publish / Build-and-publish (push) Successful in 12m51s
Details

Browse Source
This commit is contained in:
4gl
2026-08-13 13:46:43 +01:00
parent 729437308a
commit bf3ef8bab1
1 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/feed/git-for-production-data/index.md
+9 -9
View File
@@ -15,17 +15,17 @@ If you could make a "pull request" for production data, how might that look?
Perhaps: Perhaps:
- ✅ A before / after comparison of the values that had changed ([the approvals screen](https://docs.datacontroller.io/dc-userguide/)) - ✅ A [before / after comparison](https://docs.datacontroller.io/dc-userguide/) of the values that had changed
- ✅ Security (who can submit / approve in each "repo") ([EDIT vs APPROVE groups](https://docs.datacontroller.io/dcc-security/)) - ✅ [Security](https://docs.datacontroller.io/dcc-security/) (who can submit / approve in each "repo")
- ✅ Only store the changed data (not full copies) - ✅ Only store the changed data (not full copies)
- ✅ A new "diff" when the base table changes - ✅ A new "diff" when the base table changes
- ✅ Ability to choose one or more approvers ([`NUM_OF_APPROVALS_REQUIRED`](https://docs.datacontroller.io/dcc-tables/)) - ✅ Ability to choose [one or more approvers](https://docs.datacontroller.io/dcc-tables/)
- ✅ HOOK scripts before / after a commit ([pre/post edit and approve hooks](https://docs.datacontroller.io/dcc-tables/)) - ✅ [HOOK scripts](https://docs.datacontroller.io/dcc-tables/) before / after a commit
- ✅ Tests (DQ checks) prior to merge ([validation rules](https://docs.datacontroller.io/dcc-validations/)) - ✅ Tests ([DQ checks](https://docs.datacontroller.io/dcc-validations/)) prior to merge
- ✅ A pipeline following a merge ([post-approve hooks](https://docs.datacontroller.io/dcc-tables/)) - ✅ A [pipeline](https://docs.datacontroller.io/dcc-tables/) following a merge
- ✅ Emails for "status" changes ([email alerts](https://docs.datacontroller.io/emails/)) - ✅ [Emails](https://docs.datacontroller.io/emails/) for "status" changes
- ✅ Comments by reviewers - ✅ Comments by reviewers
- ✅ Full history of changes ([the History tab](https://docs.datacontroller.io/dc-userguide/)) - ✅ 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. 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.
@@ -56,7 +56,7 @@ If you're ready to "commit" to Data Control, we invite you to "clone" the latest
Link in the comments below 👇 Link in the comments below 👇
#dataops #mdm #masterdata #dataquality #sas #sasjs #datagove #dataops #mdm #masterdata #dataquality #sas #sasjs #datagovernance
--> -->
<!-- Image prompt: <!-- Image prompt: