This is pretty conducive to a Gerrit (https://www.gerritcodereview.com https://www.gerritcodereview.com) workflow. If unfamiliar, Gerrit essentially treats each

This is pretty conducive to a Gerrit (https://www.gerritcodereview.com https://www.gerritcodereview.com) workflow. If unfamiliar, Gerrit essentially treats each commit as it's own PR or "change" in Gerrit terms. It uses git's refspec as staging area so each commit basically becomes a mini branch. Changing a "change" then requires amending the commit and pushing a new "patch set". So what my team does when we want to prototype something is we create a change and then push separate patch sets for different solutions (there is a nice diff tool to view differences between patch sets). The CI runs for each patch set and we then discuss the merits of each approach and "abandon" (reject) the change and use it for reference going forward.