Connecting repo to DeployHQ ends up in Unprocessable Entity sometimes

[ecairol]

Running the command team51 deployhq:create-project ends in an error:

Running in developer mode. Skipping update check.
Please enter the name of the project to create: test1
Please select the zone to create the project in [North America (East)]: 
  [3] Europe (UK)
  [6] North America (East)
  [9] North America (West)
 > 9
Would you like to connect the project to a GitHub repository? [y/N] y
Please enter the slug of the GitHub repository to connect the project to: test1
Are you sure you want to create the DeployHQ project `test1` in North America (West)? [y/N] y
Creating DeployHQ project `test1` in North America (West).
Project `test1` created successfully. Permalink: test1
Are you sure you want to connect the DeployHQ project `test1` (permalink test1) to the GitHub repository `a8cteam51/test1`? [y/N] y
Connecting the DeployHQ project `test1` (permalink test1) to the GitHub repository `a8cteam51/test1`.
❌ API error (500 https://opsoasis.wpspecialprojects.com/wp-json/wpcomsp/deployhq/v1/projects/test1/repository): {"code":422,"message":"Unprocessable Entity","data":null}
Failed to connect the project to the repository.

On DeployHQ the project was created ok, however, the GitHub repository was not connected.

[ecairol]

Here's more information on how to reproduce this issue:

1. Use team51 github:create-repository to create a new repository. Leave the options empty
2. The CLI will ask you for a name, enter one.
3. When the CLI ask you for the type, leave that empty
4. Once the repository is created, try to link it to a DeployHQ project, either creating a new project with deployhq:create-project, or using deployhq:connect-project-repository
5. The CLI will fail to connect the Project to the Repository
6. If you create the repository using the parameters, the connection will not fail. (eg: team51 github:create-repository my-test-repo --description="Just testing" --type=plugin