@AbhaySingh , 

This was a fun read — and a great way to spark discussion about what “Git inside my database” really means in practice.

From what I’m seeing in the product world, Databricks isn’t literally putting Git inside the storage engine of your tables — it’s bringing Git workflows directly into the workspace UX so your notebooks, SQL queries, dashboards and other artifacts live in Git folders/Repos and you can branch, commit, push and pull without context-switching out of Databricks. 

That shift has a ton of practical value for teams that want classic software engineering best practices — feature branches, CI/CD, collaboration — but it’s also worth grounding expectations a bit: the Git integration is fundamentally a workspace-level source control layer, not a metadata/time-travel layer over the data in your tables. In other words, you’re not versioning your Delta lake like a Git object store here — you’re versioning the code and queries you write against it.

Curious to hear how folks are using this in real projects — especially around branching strategies and managing merge workflows across notebooks and SQL.

Cheers, Louis! 🚀