How to split commits for client/server?

Question

git

The easiest option is to separate the server and the backend into different repositories + a common repository. As a result, it becomes difficult to manage them, especially to put tags (instead of once, you need to do the same actions in three repositories).
If you keep everything in one repository, it's harder to see the commit history. This is especially true when there are a lot of commits with style changes on the client, which makes it difficult to find the commits associated with the backend.
It would be possible to add a prefix to the commit message, but this is all manual work.
Is there any way to automatically split such commits or attach labels to them?

Answer 1

the choice is the following: monorepo, subtree, submodules. Everything is described in the documentation for the git.
here, too, you need to refer to the documentation. like git log -- path/to/backendFolder and wow, magic!
bottom line: read mana. they rulez!

Answer 2

Create commits in the style:
"Client - Description"
"Server - Description"
This is how I always indicate the project module in which I made changes.
By the way, with the help git log -- path/to/backendFolderyou can see in which commits there were simultaneous changes in the client and server.