The linked website includes this workflow under their definition of trunk-based-development. As long as your branches are short-lived and make it into the main

The linked website includes this workflow under their definition of trunk-based-development. As long as your branches are short-lived and make it into the main line rapidly, it appears to be considered equivalent. I've seen some commentators say that this doesn't pass their bar for TBD, but I think it's effectively the same thing. The site does call out "GitHub flow" as being slightly different, but that's because GitHub's description of their model includes deploying the branch to production before merging to master.