actions-gh-pages VS tortoisegit

Check out the GitHub action you can use for deploying to GitHub pages: https://github.com/peaceiris/actions-gh-pages.

In addition to just sharing the .html generated files which would likely be cumbersome, you can host the docs on github pages and use something like https://github.com/peaceiris/actions-gh-pages + github actions to upload the documentation from your private repository to a public repo (required for non paid users).

I started by using runs-on: ubuntu-22.04 in this workflow to check if everything works ok. It run without any issues. After that I created PRs to add support for ubuntu-22.04 and ubuntu-latest version to GitHub Actions for Hugo and GitHub Pages Action

As a first-step measure, we changed the CI script to overwrite the gh-pages branch at every run, rather than just appending a new commit. We use this gh-pages action, so it was just a matter of adding a force_orphan: true parameter.

Interesting to note that GitHub stores this workflow in the "main" branch under .github/workflows folder. For more details on this Action please refer the documentation and code at https://github.com/peaceiris/actions-gh-pages.

My first workflow is to build and deploy or preview Client, It runs whenever a push or pull request creates for main branch containing changes to the code of client. It install dependencies and builds vue.js app. After build I use peaceiris/actions-gh-pages to deploy it to Github Pages. If the event is Pull Request then deploy to a sub-directory named preview and commit hash and leave a comment on PR.

If the data fetch from previous step succeeds, the workflow continues by building the static website with Hugo. Hugo is setup using action peaceiris/actions-hugo. When the files are ready, the result is published to GitHub pages, using another GitHub action, peaceiris/actions-gh-pages.

peaceiris/actions-gh-pages@v3 - deploys any folder(s) to gh-pages, can use it for multiple static endpoints

For more information about the actions used and their options, please see Hugo and Github pages on Github.

This quote is quite true. Without automation, we would spend a lot of out time on things that would have to be done repetitively, for example, manually building and deploying your GitHub pages every time there is a change. Luckily, you can easily use GitHub Actions to build and deploy your pages by just pushing your repository to GitHub! You don't even need to do anything except to add a configuration file to your repository. In this post, I will be creating a workflow and using peaceiris/actions-gh-pages@v3 from GitHub Marketplace (it's free).

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.