When creating rolling content views using the repository_ids parameter to directly add some repositories, then the content view is associated with the repos, but no rolling repo clone repos are created.

This means the content cannot be consumed, even though it looks like it is part of the rolling content view.

This was likely overlooked since the UI workflow always creates the rolling content view without any repos, which are then added via the update action, which works as it should.