Repository branch
Review the import and resolve conflicts.
CUVENA / GIT
From reviewed change to controlled release.
Connect repository imports with script history and promote approved versions through environments.
GIT & PROMOTION
Know where a version came from.
Connect the repository change to its review and promotion history.
Illustrative example · No customer data or live execution
Script version 4
Retain the originating commit reference.
Validate the change
Check the chosen version in its test context.
Promote deliberately
Release the approved version with its history.
A commit is provenance, not permission
Repository access, approval and target execution permissions have separate roles. Importing content must not silently approve it for production.
CUVENA SCRIPT MANAGER