Skip to content
Nexa Platform Docs

Review Changes

Review Changes is where edits you make across Nexa are staged, inspected, and committed to your Git repository as a batch. When you add or change a connector, projection, data flow, or business-glossary entry, the change is held as a pending draft rather than applied immediately. On this screen you generate the artifacts for those drafts, diff them against what is live, and push the ones you approve. It is reached from the changes indicator in the header and from the Recent Changes widgets on the dashboard (route /review-changes).

Why changes are staged

Section titled “Why changes are staged”

Nexa is Git-backed: the source of truth for your platform configuration is a repository. Rather than writing to that repository on every edit, Nexa collects your edits into a workplace draft so you can review and commit them together. This gives you a checkpoint — nothing reaches the repository until you explicitly push it.

What appears here

Section titled “What appears here”

Each pending item is one staged change. The types of change tracked are:

Change type Source
Connector Edits from the Connectors screen
Projection Edits from the Projections screen
Data Flow Edits from the data-flow / data integration screens
Business Glossary Entity, PII, and classification edits from the Business Glossary

Every item carries an action of Add or Update, who made it, and when. Once its artifacts have been generated, the item shows an Artifacts Generated badge.

You can search pending items by name or alias, and filter by item type, action (Add/Update), and whether artifacts have been generated. A count summarizes how many pending items are in your workplace draft.

The review flow

Section titled “The review flow”

  1. Select items. Tick the pending items you want to act on. A Pending Items header checkbox selects all.

  2. Generate Artifacts. Click Generate Artifacts to build the deployable artifacts for the selected drafts. Items flip to Artifacts Generated when done.

  3. Check Diff. Click Check Diff to open a side-by-side comparison titled Check Diff — Local vs Live Repository. It shows the Live Branch (Original) against the Local Branch (Generated), with the repository name and branch, and a summary of how many files are new, modified, or deleted (each file tagged New, Modified, or Deleted). Items must have artifacts generated before you can diff them.

  4. Push to Git. From the diff, click Push to Git to commit the generated artifacts to the repository. After confirming, Nexa commits the change and reports the branch it pushed to.

To drop drafts you do not want, select them and click Discard.

Actions summary

Section titled “Actions summary”
Action Effect
Generate Artifacts Build deployable artifacts for the selected pending items
Check Diff Compare generated (local) artifacts against the live repository
Push to Git Commit the generated artifacts to the repository
Discard Remove selected drafts from the workplace draft
View logs Open the audit log for an individual item

On Databricks, artifact generation and push use the platform’s change-control artifact paths for Databricks assets.
Section titled “Related”