Verdent manages Git automatically through workspace isolation. Each workspace operates on its own branch, with changes rebased to the main branch when complete.

​
What You’ll Learn

  • Use Source Control for staging and commits
  • How Verdent handles Git operations
  • Rebasing changes to master

​
Source Control Panel

For manual Git operations, use the Source Control panel (Ctrl+Shift+G / Cmd+Shift+G):
  • View changed files
  • Stage and unstage changes
  • Commit with custom messages
  • Diff view for individual files
  • Revert changes

​
Git Through Verdent

Ask Verdent to handle Git operations naturally: 
Commit these changes with message "Add user authentication"

Commit current changes as work-in-progress
Verdent reviews changed files, generates a descriptive message, and executes the commit.

​
Workspace Operations

Each workspace has its own Git branch. Use Workspace Actions in the Top Bar:
OperationAction
Sync from MainPull latest changes from main branch into workspace
Rebase to MainApply workspace changes to main branch
Create PRCreate a pull request from the current workspace branch

​
Rebase Workflow

1

Complete Work

Finish your feature or fix in the workspace
2

Commit Changes

Use Source Control (Ctrl+Shift+G) to stage changes and commit with a descriptive message
3

Test

Run tests to ensure everything works
4

Rebase

Click Workspace Actions → Rebase to Main
5

Clean Up

Click Delete Workspace in the Workspace Bar

​
Terminal Access (Optional)

For advanced Git operations, use the integrated terminal (Ctrl+J): 
# Status and diff
git status
git diff

# History
git log --oneline -10

# Reset uncommitted changes
git checkout -- .

# Reset to previous commit (destructive)
git reset --hard HEAD~1

​
FAQs

Each workspace maintains its own state. Uncommitted changes in one workspace don’t affect others.
  1. Click Workspace Actions → Sync from Main
  2. Conflicts appear in affected files
  3. Ask Verdent to help: Help me resolve the conflicts in @userService.ts
  4. Stage resolved files and complete the sync
Rebase creates cleaner linear history and easier code review. Each workspace produces a clean branch that rebases onto the main branch when complete.
Yes. Each workspace branch is a normal Git branch. Use git push origin branch-name for backup, code review, or collaboration.

​
See Also

Workspace Isolation

How workspaces use Git branches

Refactoring

Version control for refactoring workflows