Git Integration
Git Integration
Keep your saved SQL queries, scripts, and Plex stored procedures in your own git repository — with review, history, and a record of who changed what.
DataMagik can connect a repository you already own — on Bitbucket, GitHub, Azure DevOps, or a self-hosted host — and link individual items to files inside it. Once an item is linked, the editor gains a small git panel: check where it stands, pull what the repository holds, commit a change, switch or create a branch, and open a pull request.
Beta. This feature is new and marked Beta in the interface. It is in active use against real repositories; if something reads wrongly or behaves unexpectedly, tell us — the wording is part of the feature.
Where to set it up
Git setup lives on your profile, because a commit carries authorship: the token that pushes is yours, not the company's.
- Click Settings at the top right of any screen, then open the Git Access Tokens card.
- Or take the shortcut: Script Engine → Git. It opens the same page.
That page holds your access tokens at the top, and — if you are a Builder — the shared repository connections below. Full walkthrough: Setting Up a Git Connection.
The Git button does not appear in the editors until a repository connection exists. That is deliberate — most tenants never configure git, and a button whose only answer would be "add a connection first" is clutter. Add the connection, then reload the SQL Editor or Script Engine and the Git button appears in the toolbar near Save. See Reload the editor.
What it can version
- Saved SQL queries — from Script Engine → SQL Editor.
- Scripts — from the Script Engine editor. The file carries the script's settings in a header, so a script restored from git comes back configured, not just with its code.
- Plex stored procedures — through the browser extension, entirely inside Plex. See Git for Plex Stored Procedures.
How to get started
- Set up a git connection — add your personal access token on your profile, then point DataMagik at the repository.
- Work with git in the editors — match an item to a file, then commit and pull day to day.
Three things worth knowing up front
- A commit runs as you. Access tokens are held per person, not per company, so the history in your repository names the individual who pressed the button. This is why the token lives on your own profile rather than on the company credentials screen.
- Nothing is overwritten without asking. Pull never replaces what is open in the editor by itself — it reports what the repository holds and waits. A commit is refused, not merged, if the file changed in the repository since DataMagik last read it.
- Git work happens in the background. Each operation clones the branch it needs, so a check usually takes a few seconds rather than being instant. If the background worker is not running, you are told that immediately instead of being left waiting.
Permissions
- DataMagik - Builder — add, edit, and test repository connections; create branches; match items to files; commit; open pull requests.
- DataMagik - Viewer — see connections and read status. A Viewer still holds their own access token, since a token is personal.