When no builds have been configured (yet), let the rebazer still work just when someone approved it. There were some ideas flying around how to implement it (e.g. is there a special result when asking for build status, ... ).
However this may result in that there will be no changes on some hosts if there is no build, thus the logic for merging would need refactoring.
In my opinion this is only a issue when we find a valid use case for a repo without build. The argument we haven't a automated build yet isn't a rational argument and leads people to a unfavourable direction.
When no builds have been configured (yet), let the rebazer still work just when someone approved it. There were some ideas flying around how to implement it (e.g. is there a special result when asking for build status, ... ).
However this may result in that there will be no changes on some hosts if there is no build, thus the logic for merging would need refactoring.