Set repo visibility

[dylan-smith]

trafficstars

Customers have asked if it's possible to add an option to let them set a state other than private for a repo when it's done migrating. This capability is already implemented in Octoshift, so this issue tracks passing the appropriate data to Octoshift via the CLI to use this feature.

The customer can configure this in the CLI. When they run generate script we will add a --target-repo-visibility option to migrate repo that by default matches the state that the source repo was in.

Todo

• [ ] Update the CLI generate script to add a --target-repo-visibility to the migrate-repo command that adds the state that the source repo was in (i.e. private/public/internal). If the field isn't included then the default should be private.
• [ ] --target-repo-visibility should be included in for ado2gh customers. We can just default to private for that scenario.

[synthead]

Should this be added to Octoshift instead?

Edit: after a conversation with the team, this has already been implemented in Octoshift, and this feature tracks consuming this feature with the CLI! I have updated the issue body to reflect this :+1:

[timrogers]

I do definitely think we should do this. It would be easy to add in the migrate-repo command at least. I guess it's likely to be harder in generate-script, as you probably want the ability to "inherit" visibility from the source.