Godot

SmartGit - lets you see the commands it's running and has a fairly decent toolset for rebasing (but I stopped recommending them for awhile when they delisted their perpetual licensing. It looks like as of writing it's returned but only allows for 1-3 years of updates depending on how many years you buy)

I've had my eyes on lazygit and gitui as a cli supplement

On a different note, I wish git lfs wasn't such a pita. Orphaned pointers living forever on GitHub and eating up all your quota with no way to recover unless you DELETE the repo lol

Git here. Subversion for a while before that. And source safe, or as I like to say source "safe", before that.

But maybe a better question would be, what source control hosting site (if any) do you use? And do any of them not forcibly use your code to train their AI?

I've been trying out Jujutsu recently.

It's compatible with git repos. The workflow takes a little while to get used to but can be nicer to work with.

Git at work.

Mercurial for my own stuff.

Perforce when I was doing it professionally but now for hobby just github desktop.

Git for pleasure, Perforce for dayjob

Project.py

Project-v2.py

Project-v2-done.py

Project-v2.1-FINAL.py

Project-v3-FINAL-FINAL.py

Project-USE THIS ONE!.py

…

just git

Git

Magit, which is the best Git porcelain around. Git, because it has an unparalleled free-software ecosystem of developer tools that work with it.

Why is Git's free-software ecosystem so much better than all the other VCSen?

Largely because of marketing (the maker of Linux made this! hey look, GitHub!), but also because it has a solid internal data model that quickly proved to experts that it is fast and flexible and reliable.

Git's command-line interface is atrocious compared to contemporary DVCSen. This was seen originally as no problem because Git developers intentionally released it as the “plumbing” for a VCS, intending that other motivated projects would create various VCS “porcelain” for various user audiences. https://git-scm.com/book/en/v2/Git-Internals-Plumbing-and-Porcelain The interface with sensible operations and coherent interface language, resides in that “porcelain”, which the Git developers explicitly said they were not focussed on creating.

But, of course, the “plumbing” command line interface itself immediately became the primary way people were told to use Git, and the “porcelain” applications had much slower development and nowhere near the universal recognition of Git. So either people didn't learn Git (learning only a couple of operations in a web app, for example), or to learn Git they were required to use the dreadful user-hostile default “plumbing” commands. It became cemented as the primary way to learn Git for many years.

I was a holdout with Bazaar VCS for quite a while, because its command-line interface dealt in coherent user-facing language and consistent commands and options. It was deliberately designed to first have a good command-line UI, and make a solid DVCS under that. Which it did, quite well; but it was no match for the market forces behind Git.

Well, eventually I found that Magit is the best porcelain for Git, and now I have my favourite VCS.

Git

Git

Git

I don't use version control.

discoball

Git

CVS.

Wat?

Git with Fork as a client.

Git / TortoiseGit

Git

I used to use the OpenVMS file system for informal version control, while I was developing something and before it was ready to be committed to the repository.