We host the bitrise.yml together with our codebase in our GIT repo, but cannot add or rename workflows to it and make a test run of them before merging to the main branch, as only workflows from the main branch are listed in the Schedule Build dialog.
To make the config file follow our current GIT flow, we create feature branches, make changes to code and build config there (which are often connected somehow. e.g. adding a new script to the codebase which you want to call from Bitrise), but as the workflow names are always pulled from the main branch, we cannot add new workflow names to a feature branchs bitrise.yml, and trigger them on the build server before they are actually merged to main.
It would be great if there was a possibility on the Schedule Build dialog to either:
- fetch workflow names from the branch name you enter in the dialog
or
- enter a custom workflow name in the Workflow drop-down box.
Any suggestions for how to otherwise achieve this is very welcome :)
We host the
bitrise.ymltogether with our codebase in our GIT repo, but cannot add or rename workflows to it and make a test run of them before merging to the main branch, as only workflows from the main branch are listed in the Schedule Build dialog.To make the config file follow our current GIT flow, we create feature branches, make changes to code and build config there (which are often connected somehow. e.g. adding a new script to the codebase which you want to call from Bitrise), but as the workflow names are always pulled from the main branch, we cannot add new workflow names to a feature branchs bitrise.yml, and trigger them on the build server before they are actually merged to main.
It would be great if there was a possibility on the Schedule Build dialog to either:
or
Any suggestions for how to otherwise achieve this is very welcome :)