Skip to main content

Differences Between VS Code and Jupyter Lab When Using Git

Inside the Processing and Intelligence modules, you can use both VS Code (see the setup guides here) and Jupyter Lab, which is native to the modules. However, there are restrictions when using Git from inside VS Code.

What works in VS Code?​

In VS Code, you can run local Git commands, meaning commands that do not require communication with the remote repository.

git log                 # View commit history
git status              # Check the working tree status
git add nome-do-arquivo # Add files to staging
git checkout -b nova-branch # Create and switch to a new branch

📌 These commands work because they do not depend on the remote repository.

What does NOT work in VS Code?​

Commands that require interaction with the remote repository (GitHub, GitLab, and so on) do not work in VS Code.

Examples of commands that do not work:

git pull origin main       # Pull changes from the remote repository
git commit -m "DOCS: This commit will not work in VS Code"  # Create a commit
git push origin minha-branch  # Push changes to GitHub

Where should you run remote commands (commit, pull, push)?​

For commands that involve the remote repository, use the Jupyter Lab terminal:

git pull origin main # fetch updates from main
git commit -m "Adding new feature"
git push origin minha-nova-branch # push the new branch to the repository

📘 Summary

🔹 To view history, check status, and stage files, you can use VS Code.

🔹 To run commit, pull, and push, use the Jupyter Lab terminal.

CommandWorks in VS Code?Works in Jupyter Lab?
git log✅ Yes✅ Yes
git status✅ Yes✅ Yes
git add nome-arquivo✅ Yes✅ Yes
git checkout -b branch✅ Yes✅ Yes
git commit -m "msg"❌ No✅ Yes
git pull❌ No✅ Yes
git push❌ No✅ Yes

💡 You can also work exclusively in Jupyter Lab if that is your preferred workflow.

💡 And remember that VS Code supports many extensions that can add significant value to your development environment.