Oracle AI Data Platform Workbench Git integration, currently in preview, helps teams connect Workbench to external Git repositories so they can ingest, read, write, and manage project files without leaving the platform. Teams can create Git folders, connect them to a repository URL and branch, and use familiar actions such as pull, push, commit, merge, compare, and branch management from the Workbench UI without ever leaving the platform. Instead of manually downloading files, switching to an external Git client, and re-uploading changes, your entire version control workflow now lives in one place.
Why it matters?
With Git folders and bundles, teams can version important assets, push updates to a shared repository, and pull those changes into other workspaces while keeping related resources and dependencies together. You can package jobs, notebooks, compute definitions, and agent flows into a deployable artifact and promote it across environments with all connections and dependencies intact.
Three practical tips to get started:
Set up dedicated credentials per repository.
Rather than sharing one credential set, create separate Git credentials for each repository or access level (read-only vs. read-write). Navigate to your workspace settings, add credentials, and select them when creating a Git folder. This makes it easy to rotate keys or revoke access for a single integration without affecting others.
Treat rebase and reset as last-resort operations
Both require a force push, which rewrites remote history. In collaborative projects this can overwrite a teammate's commits. Use standard pull → resolve → commit merge for day-to-day sync, and reserve rebase/reset for solo branches or explicit team agreements.
Use Bundles for environment promotion, not ad-hoc file copies.
When you're ready to move work from dev to production, create a Bundle (Actions → Create Bundle), select the resources to include, and deploy. This preserves connection references and dependencies that are easy to lose when copying files manually.
A few best practices
Use separate credential profiles for different repositories or access levels, grant Git folder permissions carefully, and pull before pushing so teams can resolve conflicts early.
For implementation details, start with a small repository, choose the branch when creating the Git folder, and test the workflow with a simple file or bundle before moving shared assets.
For full setup instructions, supported operations, and RBAC permission details, see the official documentation:
Git Integration — Oracle AI Data Platform User Guide
