I‘ve written before about how useful Pull Requests (PRs) are when it comes to content creation, so no need to go into too much detail here again. Basically you can use PRs as content quality gates, a place to house changes before incorporating them into production, work on them collaboratively whether that's with humans or LLMs, run automated processes on said content, and finally safely merge the content into the main production branch.
You want to make content creation as frictionless as possible, using draft branches as collaboration sandboxes, but have explicit control on what makes it into production, and PRs are a tried and tested way to do that. The PR is an explicit decision point where you can promote or reject content, ensuring you not only have complete control on what ends up in production, but that you also have an audit trail should you later want to remember what changes were made along the way.
By using Git branches as flexible sandboxes and PRs as intentional quality gates, content production becomes both frictionless and reliable. You get the freedom to draft rapidly, alongside human colleagues and AI agents, without sacrificing total editorial control over what hits production.