Fast Git client
packed with all features.

FIG 1THE TOOLKITCLICK A SCREENSHOT TO ENLARGE

1. 01history

   Repository history

   Navigate through your commit history with an intuitive graph visualization. The timeline shows the complete evolution of your codebase, making it easy to understand complex branching strategies and track the development flow.

   • All branches combined: see every local and remote branch in a single graph, with all merges and forks at a glance.
   • Individual branches: focus on a single branch and hide everything else to follow its history without distraction.
   • Branch badges: commits are labeled where each branch begins and where its tip currently points, so you always know where a line of work started and how far it has progressed.
   • Tag badges: tagged commits are clearly marked, making releases and other milestones easy to spot in the history.
   historyhistory-dark.png
2. 02merge

   Merge conflict resolution

   Resolve merge conflicts with a merge interface that keeps your changes, their changes, and the merge result in context. Visual indicators highlight conflicting regions, and you can choose changes from either side with confidence.

   • Three-pane layout: both sides of the conflict are shown next to each other, with the editable merge result directly below.
   • Pick a side per conflict: use the markers next to each conflicting block to take the change from one side or the other, or edit the result by hand.
   • Conflict navigation: jump to the previous or next conflict with the arrow buttons, so nothing is missed in longer files.
   • Conflicted files at a glance: files with conflicts are listed with the rest of your changes. Save a resolved file, stage it, and move on to the next one.
   • Finish or back out: complete the merge with a commit once everything is resolved, or abort it and return the repository to its previous state.
   mergemerge-onflict.png
3. 03diff

   Side-by-side diff comparison

   Review code changes using a clean diff viewer. Choose between side-by-side or unified modes with readable syntax highlighting. The diff engine highlights changes at the line level so you can quickly understand what changed between commits, branches, or files.

   • Side-by-side or unified: switch between the two layouts with a single click, depending on whether you prefer to compare the old and new versions next to each other or read the changes inline.
   • Aligned panes: both sides of a side-by-side diff stay line-aligned and scroll together, so matching code is always next to each other.
   • Clear change highlighting: removed lines are marked in red and added lines in green, with line numbers for both versions.
   • Syntax highlighting: code keeps its language-aware colors inside the diff, so changes are as easy to read as in your editor.
   • Change overview: markers next to the scrollbar show where the changes are in the file, so you can jump straight to them.
   • Browse changed files: pick any file from the flat or tree file list to open its diff instantly.
   diffside-by-side-diff.png
4. 04blame

   Git blame

   Trace each line back to the commit and author that introduced it. Git blame makes it easier to understand why code changed and find the right context when investigating an issue.

   • Line-by-line annotation: every line of the file is shown with its line number and the author who last changed it, right next to the code.
   • Full file context: blame shows the complete file, not just a fragment, so you can read the annotated code in context.
   • Syntax-highlighted code: the source keeps its language-aware colors, so the annotated file is as readable as in your editor.
   • Open from the file list: start blame for any file in the repository straight from the flat or tree file view.
   • Faster investigations: see at a glance who to ask about a piece of code, and which parts of a file were written by whom.
   blameblame.png
5. 05gitflow

   GitFlow and other workflows

   Follow standard GitFlow workflows with a clear view of branches and release paths. Keep feature, release, and hotfix work organized throughout the development cycle. GitFlow is not the only option. Sourcerer also supports:

   • GitHub Flow: a lightweight model where you branch off main, open a pull request, and merge back once it is reviewed and ready to deploy.
   • GitLab Flow: feature branches plus environment or release branches, such as staging and production, so changes are promoted in a controlled way.
   • git-flow-next: a modern take on GitFlow with configurable branch types, prefixes, and merge strategies.
   • Graphite: stacked branches that split large changes into small, dependent pull requests that are easier to review and keep rebased.
   • Custom workflow editor: define your own branch types, base branches, naming conventions, and merge targets to match how your team works.
   gitflowgitflow.png
6. 06lfs

   Git LFS

   Manage large files with full Git LFS support. Keep repositories efficient while working with assets and other files that are too large for standard Git storage.

   • Track files from the context menu: right-click any changed file and use the LFS menu to add it to, or remove it from, Git LFS tracking.
   • No manual .gitattributes editing: Sourcerer writes the LFS tracking rules for you, so binaries, installers, and media files are handled consistently by everyone on the team.
   • Smaller, faster repositories: large files are stored as lightweight pointers in Git history while their content lives in LFS storage, keeping clones and fetches fast.
   • Works with your normal workflow: stage, commit, push, and pull LFS-tracked files the same way as any other file, without switching to the command line.
   lfslfs.png
7. 07issues

   Issue trackers integration

   Browse and manage issues without leaving Sourcerer. Connect your repository to GitHub, GitLab, Bitbucket, Azure DevOps, or any custom URL issue tracker and keep your tasks right next to your code.

   • Built-in tracker tab: the issue tracker opens in its own tab inside Sourcerer, next to your repositories, so you can switch between code and issues instantly.
   • The full tracker experience: work with the tracker's own interface, including filters, labels, milestones, and assignees, exactly as you know it from the browser.
   • Simple navigation: back, forward, and reload controls let you move around the tracker without opening a separate browser window.
   • Configured per repository: each repository can point to its own tracker, whether it is hosted on GitHub, GitLab, Bitbucket, Azure DevOps, or a custom URL.
   issuesissue_tracker.png
8. 08ssh

   SSH key management

   Configure individual SSH keys per domain or subdomain, so each Git host uses the right identity automatically. Generate new keys directly in Sourcerer or use the ones you already have.

   • All keys in one place: a dedicated SSH keys tab lists every host with its key name, private key path, and creation date.
   • Generate new key pairs: create a new key with a name of your choice, such as id_rsa_github or id_rsa_gitlab, without touching the command line.
   • Add existing keys: register keys you already use and assign them to the hosts they belong to.
   • One identity per host: keep separate keys for GitHub, Bitbucket, Azure DevOps, or your company server, and Sourcerer picks the right one automatically for every clone, fetch, and push.
   • Edit and clean up: change a host's key assignment or delete entries you no longer need.
   sshssh_key_management.png
9. 09credentials

   HTTP/HTTPS credentials management

   Store repository credentials in an AES-encrypted vault whose master key is kept in your operating system's credentials wallet. Each credential is assigned to a local repository path, so every repository signs in with the right account.

   • Secure by design: passwords and access tokens are never stored in plain text. The vault is encrypted with AES, and its master key is protected by Windows Credential Manager, the macOS Keychain, or the Linux secret service.
   • Per-repository accounts: use different accounts for work and personal projects, or for different clients on the same Git host, without credentials getting mixed up.
   • Overview of stored credentials: a dedicated Git credentials tab lists each repository path with its username and the date the credential was stored.
   • Easy maintenance: update a credential when a password or token changes, or delete the ones you no longer need.
   credentialscrdentials_management.png
10. 10worktrees

    Git worktrees

    A worktree is an additional working directory linked to the same repository. Check out several branches side by side, each in its own folder, without stashing, re-cloning, or losing your build state. It is ideal for hotfixes, reviews, and long-running builds.

    • Worktrees panel: all worktrees of the repository are listed in their own sidebar panel, next to branches, tags, stashes, and remotes, with the branch each one has checked out.
    • Quick creation: add a worktree in a few steps. Pick a folder, choose an existing branch, or tick "Create new branch" and give it a name, then confirm.
    • Open with a single click: open any worktree in a new container and work on it with the full set of Sourcerer tools, while the main working directory stays untouched.
    • Lock and unlock: lock a worktree to protect it from pruning, for example when it lives on a removable drive or a network share, and unlock it when it is no longer needed.
    • Clean removal: remove a worktree when you are done, and Sourcerer cleans up the linked working directory for you.
    • Shared history: every worktree uses the same repository, so commits, branches, and tags made in one are immediately visible in all the others, with no extra clones and no wasted disk space.
    worktreesadd_worktree.png