# Version control

Use the Workspace to review and preserve changes made by you, collaborators, or automation inside the sandbox.

## Review before committing

Inspect the working tree and diff. Separate generated files from intentional source changes, run the relevant tests, and verify that no secret or environment file is included.

Create focused commits with messages that explain the outcome. A commit is a durable checkpoint and makes later review or rollback safer.

## Branches and remotes

Create or switch branches before unrelated work overlaps. Fetch before comparing remote changes, then pull or merge deliberately. Resolve conflicts in the editor and rerun tests after resolution.

Pushing requires repository credentials with the appropriate access. Keep those credentials in the platform's secure integration or secret storage rather than project files.

## Workspace and SDK together

SDK automation can create checkpoints, branches, commits, merges, and remote operations. Open the same sandbox in the Workspace when a human needs to inspect or resolve the result. Both interfaces see the same Git working tree.

For programmatic operations and cloning a sandbox repository to another path, see [Git](/docs/sdk/git).