Earlier quoted context omitted.
I find the idea of using Git for comments somewhat terrifying, not least of all for the permanence of the history making moderation a nightmare.
They are just bunch of static hosted .jsonl text files, one comment per commit, and makes up exactly one line In case of comments you don't like, just delete the line and `git commit` to erase the history entirely, use `git cherry-pick` and `git push -f` It might be a nightmare for people not familiar with `git`, but for folks running a static blog like Hugo, they use lots of shell commands anyway.
Allowing force-push is considered an antipattern for Git, and generally best avoided. It's a safeguard against lost history and prevents data loss.
That aside, the comments are the history. Git is the wrong tool for the job. Why would you choose a generic version-control system designed for source code diffs & merges for the specialised task of chronologically-ordered comments? A database such as PostgreSQL is a far superior choice in just about every possible way. I admire your ingenuity here to make something out of what's available, but I respectfully disagree with this being a good way to capture user-generated content when there are better alternatives.