I think trunk based development only makes sense you do pair-programming and don't need a code review, otherwise simply branch from master (no dev branch needed) and rebase master + squash/fixup (also git rebase) your branch after the review is ready and merge it.
I think trunk based development only makes sense you do pair-programming and don't need a code review, otherwise simply branch from master (no dev branch needed) and rebase master + squash/fixup (also
git rebase) your branch after the review is ready and merge it.See also - guides.github.com/introduction/flow/