Deploy your Code

dex makes it easy to manage your code using Git—without ever leaving the platform. From reviewing file changes to pushing to production, everything can be done directly within the Git tab under the Develop section of the sidebar.

This guide walks you through how to commit, push, and pull changes inside dex, along with how to access your commit history and manage resets.

Making a Commit

To create a commit in dex, open the Git tab from the left-hand Develop menu. You’ll see a list of all files that have been created, modified, or deleted since your last commit.

Clicking on any file will open a diff view in the code editor, showing you the exact changes that were made. This is your chance to review the updates before finalizing them.

Once you’ve reviewed your changes, check the box next to each file you want to include in the commit. Then, enter a commit title and an optional description to summarize the purpose of your changes. When you're ready, click Commit to save your changes locally to the current branch.

Pushing Changes to Your Repository

After committing your changes, you can push them to your remote Git repository by clicking the Push to the Repository button located at the bottom of the Git tab.

The destination branch is defined by the environment you are currently working in. For example, if you're in the dev environment, your push will go to the branch configured in your dev environment in your GitHub or GitLab repository.

Once pushed, your changes become visible to your team and are available to any Flows, automations, or scheduled jobs running from that branch.

Pulling from Another Branch

To bring code from another branch into your current environment, select the source branch from the dropdown menu at the top of the Git tab. Then click the Pull button.

dex will fetch the latest commits from that branch and apply them to your working branch. This is useful when promoting changes from development to production or syncing updates made by other team members.

Viewing Commit History and Resetting Your Branch

At the bottom of the Git tab, you’ll find the commit history for your current branch. Each entry shows the commit message, timestamp, and author, giving you full traceability of every change.

From this section, you also have the option to reset your branch. You can choose a soft reset (which keeps your file changes but rewinds the commit history) or a hard reset (which resets both commits and files to a previous state). Use these features carefully, especially in production environments.

Promoting Code from Development to Production

To keep your development and production environments clean, safe, and in sync, dex supports a Git-based deployment workflow. This approach mirrors best practices used in software engineering: code is first developed and tested in a dedicated branch (such as dev), and only promoted to production (typically mapped to the main branch) once it's stable and validated.

Below is the recommended workflow to promote changes from development to production using dex’s Git integration.

1

Start in the dev branch Write and test your models, configurations, and transformations in the dev branch. Use dex’s preview, run, and validation tools to ensure everything works as expected.

2

Validate your changes

Confirm that your models run without errors, your tests pass, and your outputs look correct. Make any necessary adjustments while still in the dev environment

3

Switch to the production environment

In dex, switch your environment to production (usually mapped to the main branch in your Git repo)

4

Pull changes from dev into main

Use the Git tab in dex to pull the latest version of the dev branch into the main branch. This brings your tested work into the production workspace

5

Review and stage the changes

dex will show you a list of updated files. Review the changes, stage the files you want to include in the deployment, and add a clear commit message

6

Commit and push to main

After staging your changes, commit them and push to the main branch. This officially promotes your code to production

7

Trigger your production workflows

Now that your production environment is running the latest version of your code, any Flows or automations tied to the main branch will use the updated logic