Git upgrades & GitLab support
Git integration updates
On our Git integration front, we’ve reworked the three core actions: pull, commit, and push. Everything got a more polished UI, plus a set of improvements that make day-to-day collaboration smoother.
Support for merge conflict resolution
Previously, pull only supported fast-forward updates, which meant it worked only when branches weren’t divergent. Now you can pull even when branches diverge, and if Git can’t resolve conflicts automatically, Deepnote will show a conflict resolution modal where you can keep either your local changes or the incoming changes.
Pull with stash
No need to commit local changes just to pull anymore, even if they touch files updated on the remote. Deepnote can pull with stash, and if conflicts occur (between your local-only commits and remote, or between the stash and remote), you can resolve them in the same conflict resolution flow.
Commit and push
The commit and push modal got a big refresh:
- Preview your changes in a clean diff editor
- Exclude files from the commit
- Switch to a new branch directly from the modal
- Get prompted to open a PR after a successful push
We’ve also included a set of smaller improvements, including a clearer branch selector (with more intuitive new-branch creation) and a one-click shortcut to open your repository on GitHub directly from the integration menu.
GitLab support in Git integration
GitLab is now fully supported in Deepnote’s Git integration in the Files section - not just for exports.
You can now:
- Connect GitLab repositories to folders
- Pull changes from the remote
- Commit and push local changes
- Switch between branches
One key difference compared to GitHub: for GitLab, Deepnote performs Git actions on your behalf, whereas GitHub uses Deepnote’s GitHub App. As a result, the setup flow is slightly different. Full instructions are available in the new GitLab integration documentation.