cz-cli VS tortoisegit

Adopt a convention like commitizen: https://github.com/commitizen/cz-cli

'typeofchange(scopeofchange): reason for change'

It sort helps force devs to type out more meaningful commit messages.

Commitizen Define a interface to write your commits and automatically and a prefix and a suffix to your message. (and others features not related)

Conventional commits are great, especially if you add in commit linting.

Being able to programmatically increment semantic versions and automatically generate relevant changelogs is awesome.

It’s also nice to implement Commitizen[0] for a little hand holding until folks get used to the linting.

I used to care a lot about doing things the way that felt right to me, but now I just want some common standard that is easy for everyone to follow, easy to automate, and easy to verify programmatically.

Things like conventional commits and semantic versioning aren’t perfect, but they are quite good and apply broadly to many use cases with common tooling and conventions.

--

[0]: http://commitizen.github.io/cz-cli/

In the world of software development, maintaining consistent code quality and ensuring that the codebase adheres to predefined patterns and guidelines is crucial. However, manually enforcing these standards can be time-consuming and error-prone. This is where automation tools like Husky, Lint-Staged, Commitlint, and Commitizen come to the rescue. In this post, we will explore how these tools can be combined to streamline your development workflow.

Conventional commits specification contains a set of rules for creating an explicit commit history, which makes it easier to write automated tools on top of, for example, semantic release. You can manually follow this convention in your project or use a tool to assist you, such as Commitizen.

When working with JavaScript projects, managing version numbers and commit messages is important for the maintainability of the project. Since 2020 I have been the main developer of Atomic Calendar Revive a highly customisable Home Assistant calendar card, I found maintaining versions and releases to be cumbersome until recently. In this article, I will introduce the commitizen and semantic-release packages for creation or appropriate commit messages and semantic versioning. I will also provide examples of how I am currently using these packages to streamline my release workflow and project maintenance.

I use Commitizen to enforce a strict commit message. It's not required - but it makes my life easier. It adheres to a standard - but it's certainly not "the" standard.

When I googled, I found cz-cli project first: https://github.com/commitizen/cz-cli

Same thing with git commits. Something like commitizen. It forces a specific format of your commits. And if you're using an associated issue/bug tracker that can automatically link to commits you can set up to format like that.

That may also serve as a good entry point for nodeJS via the tools: commitizen, commitLint. That is you implement them within your project, and then also think about how to implement via CI/CD remotely.

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.