Hi @brandon_owensby_2976 ,
Thanks for the feedback, we appreciate it :)
There's definitely a value in building before merging; if you haven't already, I'd check out that feature branch article, as it outlines the pattern we use for it.
In general, the way I would try to configure is:
consider using a releaseless-build if you don't yet know the release it's targeting
use a different piepline so it's visually clear; the stages may be Build -> Test -> Merge
clean up the builds aftewards
That said, this isn't the most popular workflow in BuildMaster, so it may not be the most intuitive to implement or feel a bit clunky.
We don't have a lot of public examples, but the inedo-docs application is the closest to a Gitflow, releaseless type of workflow. Commits to master branch auto-deploy to live site, where as branches can only go to test:
https://buildmaster.inedo.com/applications/136/overview
No idea if that's helpful, but just FYI
Cheers,
Alana