The master branch requires multiple datasets upstream to update, to do incremental joins, so I don’t want devs to be able to build on master, as this could lead to missing data during the joins.
However, I want devs to be able to still iterate on the code on branches and test alternative implementations.
How can I allows those devs to run builds on branches but not on protected branches like master ?
Hi @yushi - Great answer - was not even aware this was possible.
Could you elaborate whether this is also available through the UI and not just via backend endpoint? I looked in the code repository options, but was not able to find it.