Source control and saved changes
Review saved diffs, stage deliberate changes and keep local commits distinct from remote synchronization.
In the Windows app, Git works on projects in folders on your PC. Install Git for Windows in its default location; DDS runs C:\Program Files\Git\cmd\git.exe. Without signing in, you can still edit and save files and use local Git; sign in to connect a Git account and use Fetch or Push. Managed server jobs do not turn a local folder into a Linux workspace or authorize arbitrary Git commands.
Before using Git
Open a Git-backed project and save editor changes before reviewing Source Control. Confirm the repository root and current branch. Git works on saved files and the index; unsaved editor text can differ from the displayed diff.
Review, stage and commit
Refresh status and open the working-tree diff for each intended file.
Stage only the changes you intend to include. Review the staged diff, including new files and deletions.
Write a commit message describing the change and commit when the current host exposes that action.
Read status and history again to confirm the resulting commit. A local commit remains local until an explicit remote transfer succeeds.
Cloud provider connections
In the Windows app, connect GitHub or GitLab in Settings → Desktop → Developer tools → Git accounts. Use this flow on another host only if it actually offers Git accounts; Developer access alone is not a Git connection screen. Then, in the project's Git settings, choose the repository and branch and use Fetch branch or Push current commit. Fetch stores the remote branch locally; Push sends the current commit without forcing remote changes. If the service has not enabled connections, DDS shows "Git account connections are not available in this environment yet."
Project write permission and provider repository access are both required. A changed account, organization, workspace or provider connection can invalidate a pending operation. Keep provider credentials in the account connection flow, outside repository files and terminal arguments.
Conflicts and recovery
If a save or Git operation returns an uncertain result, read status, diff and history before retrying. Repeating a commit or push blindly can create duplicate work. Preserve unrelated changes and recover on a separate branch or copy when appropriate.
The native Linux CLI uses alti ide workspace git with its own supported operations. Existing WSL projects on older supported releases use their Linux workspace adapter. Neither path should be treated as an arbitrary Git shell. See CLI workspace operations and Local workspaces.