@Bdellar Thank you for the response. I think I understand more about where you're coming from now.

So one could say that trunk-based dev as a Git workflow (specifically where you commit directly to main/master) forces some level of collaboration by making changes more synchronous in nature?

Where as using PRs (even in trunk-based dev) requires a more deliberate approach to collaboration (e.g., the workflow doesn't force it but it can still be done if care is taken).