When our schedule is not filled out, the monthly release issue can't be created using release-tools
release-tools
relies on the fact that it can parse the schedule for the next release. If the next release is not in that schedule, we get an empty string, which prevents the create_issue
method from working properly. We should probably still allow the monthly release to be created and assign it to no one. That way the person trying to run the task still has the ability to create the issue with problems.
Use this issue to tackle better error handling around a missing schedule, and being able to create the issue without any assignee. (Currently this results in a 400 from the Issues API)