Git commits should be focused on one small thing at a time, doing small changes or additions. Then using descriptive commit messages like “add webook notifications” or “fix webhook triggering twice”.

This makes the history of the project easier to see what changes were made and for what purpose. If something breaks webhook functionality then you can have an easier time finding what broke that feature. It also has the added benefit of someone showing their work progress. It’s like you can be a math genius but if you don’t show your work, your professor is going to think you cheated. In this case, it’s a pretty dead giveaway that AI was involved. Since you are using AI then smaller commits also let you see what the AI to changing between iterations since even if you give it a copy of a file, it may change other parts of that file that you didn’t ask for, and those changes could be good or bad.

And just because you are making these commits doesn’t mean you have to “git push” them to your public repo right away. Since you’re working alone and don’t have any community contributors then you can just keep that work locally and push when you’re ready for the next public release. Over time you could start using a development branch in git and push to that, so other developers can see your progress and when you’re ready for a public release your merge the changes to your main branch. That’s some more advanced git stuff but it’s a core skill of any developer to be able to use branches.

Also there’s nothing wrong with being new. I only mentioned the new account because when combined with the other things, this was a dead giveaway of AI use.

For what it’s worth, good job putting together something that is useful for you. I would just encourage you to make sure you are trying to understand what you are doing and be willing to challenge yourself instead of using AI as a mental crutch like many people do. AI can only get you so far and you’ll need to learn enough to call its bullshit and point out its mistakes.