OP might well be talking about that, but it doesn't match what some close to authoritative sources would understand as "trunk based development":
Atlassian: https://www.atlassian.com/continuous-delivery/continuous-int...
trunkbaseddevelopment.com: https://trunkbaseddevelopment.com/
Both of which describe having short lived branches. Atlassian is more aggressive with their timescale of "short lived", suggesting they should be closed out daily.
This contrasts with the "gitflow" model of development with long lived feature branches, which can live across multiple sprints.
It also doesn't make sense in a git based world, because there isn't much difference in concept or outcome between local and not-yet-pushed commits to local main vs a local branch.
The local branch just has a nice description and makes it slightly easier to organise the merge back to remote main later.
In both cases, you'd have the same (if any) merge conflicts, ultimately you have a situation where you need to merge, say, local commit 81f0f61e1 into remote shared history commit efe3c586c and, say, remote (latest) commit d224e5b7b.
In both cases I'd recommend merging remote main into the branch / local main to get a single commit on your local main/branch with both shared histories so there's no conflicts. IF there are conflicts trying to do that, resolve it with a local merge commit and manual conflict resolution.
That you happen to name your local commit at the point of divergence is a convenience for more easily controlling when to merge commits, and to enable switching back to a shared history more convenient. (git switch main is easier to remember than git checkout <hash>).
If OP is claiming to "not have branches" then they still do have a logical equivalent to branches, just without some of the tooling that branches make quicker.
Edit: Edited to avoid suggesting what "most" people think, because that is hard to judge.