academia-hugo VS tortoisegit

Every Hugo site has an associated theme to apply the site style and look. I decided to use the freely available Academia Hugo theme, and since I might need to make changes to the theme files I decided to fork their Git repo to my GitHub account.

There is also a TortoiseGit that is based on TortoiseSVN

https://en.wikipedia.org/wiki/TortoiseGit

https://tortoisegit.org/

TortoiseGit sourcetree git kraken some times you need to compare to files you can do this with the notpad++ compare plugin or with Meld

Instead on my PC I use TortoiseGit. Most useful for the git log (as a graph), diff with previous versions,, filter files to commit by directory and ability to exclude files from the current commit, and most of all; ease of splitting a commit for each single file into parts by ability to "restore after commit" which allows you to edit a file before the commit and have it automatically restored to the pre-commit state afterwards.

If running TeXStudio in Windows, my personal preference is to keep the automatic check-in disabled and to use the manual one (File -> SVN/git -> Check in); this allows an individual commit message with the briefer abstract line, empty line, and the longer report. Perhaps it is less exhaustive then a proper git client (in Windows e.g., tortoise), yet TeXStudio' GUI and integrated version control allows to resolve many typical situations. The developers document as advanced use; heck, after some time, it becomes second nature. In case of missing git-related functionality, you still can opt for an other git GUI or for git from the command line independent of TeXStudio's choice.

> We now have a large selection of tools that allow you to visualize what's going on (I use git-kraken), as well as google for help on doing something that isn't in muscle memory.

Git Kraken is excellent, though Git has a page on various GUIs, many of which are free with no restrictions: https://git-scm.com/downloads/guis

Personally, on Windows I like SourceTree: https://www.sourcetreeapp.com/

Some that have worked with SVN back in the day like TortoiseGit: https://tortoisegit.org/

On *nix Git Cola seems to do the job for me: https://git-cola.github.io/

Then again, the most complex workflow I've worked with was Git Flow and I didn't need anything more advanced than that. Come to think of it, I don't really do rebases often either and mostly just take advantage of squashing commits through GitLab/Gitea and such, when needed.

But hey, that's also valid, using Git in a way where you get version control but mostly keep the technical details out of your way (though Git LFS and certain cases with particular line endings being needed does make you drop down occasionally).

The method to add the illustration to git, either from the command line, or via a GUI (for example TortoiseGit) should not have an influence how the image is managed by git itself. There is no "watermark" like stamp on the picture from which you later could tell if the picture, or the edit on the picture was committed from the CLI, or e.g., tortoise, either.

I started with TortoiseGit (coming from TortoiseSVN), then used SourceTree for a while (until Atlassian broke it. I hear it is better now), but I’ve settled in GitKraken for my work stuff where I need to maintain full histories while ping-ponging code features between many branches. I’ve heard great things about GitTower too.