At the time of writing, bitrise.io supports only one workflow per trigger (pull request, push to branch or tag). There is a related feature request. Fortunately this limitation can be easily mitigated.
The solution depends on your goal:
- You need separate workflows for some cases but sometimes you just need to run one after the other and you have enough build time (see here for more details).
In this case you can use utility workflows, they are basically chains of the normal workflows. More info can be found on devcenter.
- You don’t have enough build time to accommodate all the workflows (e.g. you have mutation tests which require a lot of time).
The solution consist of using Build Trigger API. It can be invoked for example from script step using curl command. You need a token from
codetab of your app. Keep in mind that out of the box PR status checks in the workflow triggered via API will work only if you provide a commit hash however, you can add GitHub status step to that workflow.