nostr:npub19cvahxwvggsl00neu2fc2gjtut2uwm0mp6quyyw4p87s33z4xdtqfmqnc3 Well, they can use git, why not. But they need a mentor that tells them:

* don't put generated things into git (like binaries), use .gitignore
* don't use comments like "updated", ideally write comments that "sell" the changes like Linux kernel commits do
* don't put 7 unrelated things into one. commit, "git add -i" or even better msgit is a thing (that allows you to select a single line change to commit, even when you currently have hundreds of lines changed)
* before pushing, "git rebase -i" is a thing to make your mess more structured. Again much nicer UX if you use magit
 
That will get you a king way into not creating mess.

Also teach them about your local commit police (kernel or sourcehut like email approach, github-like approach with short lived feature branches snd PRs). This depends on the project and changes alot. But you cannot expect a newbie programmer to know about it, so you gonna need to teach them.