Git for your team.
Without having to learn Git.
If you like, CodeShuttle runs your sync folder as a Git repository itself: every sync creates a commit automatically, and in a team CodeShuttle exchanges states via a network share or your Git server. You click "Synchronise" – the rest happens on its own.
As much Git as you want.
The mode belongs to the project, not to the computer: whoever opens the same sync folder works in the same mode. CodeShuttle never touches an existing, self-managed repository unasked.
Off
Plain sync between TIA and folder – no versioning. Ideal if you already drive Git yourself.
Local
CodeShuttle creates the repository and commits automatically after every sync. No server at all – perfect for single seats.
Shared
Additionally pulls before and pushes after each sync – against a network folder (UNC) or a Git server via HTTPS.
Expert
Your team does branching, pull and push itself – with the Git tool of its choice. Auto-commit optional.
One click. Five things happen.
So that nothing is ever lost – even when two colleagues work at the same time.
Every change with name, date and content.
The history shows the latest 200 commits right inside CodeShuttle. Compare any file with the current state and bring back an earlier version in two clicks – the next sync then transfers it into TIA.
- Author picked up automatically – from the Author card in CodeShuttle, your global Git configuration or your Windows user name
- Consistent commit messages in English, so the whole team reads them the same way
- Nothing is lost: restoring only replaces the file, the previous state stays in the history
Replace the current file "Foerderband.scl" in the sync folder with the state from this commit? The current state stays in the history.
Restore fileCancelMerge conflicts without a command line
If two colleagues changed the same file, CodeShuttle pauses and shows both versions side by side. Per file you choose "my version" or "team version" – done. Your state is always kept as a safety commit.
Your server, your rules
A shared network folder is enough – CodeShuttle creates the remote there itself. Or use any Git server with HTTPS access: GitLab, GitHub, Azure DevOps, Gitea, Bitbucket.
Secure sign-in
Personal access tokens are stored encrypted under your Windows account – never in the log, never in a commit. Environment variables are available for service accounts.