Describe the bug

Creating an Organization Secret via github.com allows you to specify the "selected repositories" visibility setting, and initially specify zero repos (you can update the list later).

https://docs.github.com/en/rest/actions/secrets?apiVersion=2022-11-28#create-or-update-an-organization-secret confirms the selected_repository_ids parameter is optional / not required.

Whereas using gh secret set somesecret -b somevalue -o orgname -v selected will error out.

Steps to reproduce the behavior

1. Create an Organization secret, specify Selected Repositories for Visbiility, but don't specify any repositories.
2. Confirm the secret is created.
3. Create a Personal Access Token with Organization Secret level permissions (read/write)
4. Then try gh secret set somesecret -b somevalue -o orgname -v selected using the Personal Access Token - error.

Expected vs actual behavior

Expected: secret gets created, with "selected" visibility and no repositories specified.

Actual:

> gh secret set somesecret -b somevalue -o orgname -v selected
`--repos` list required with `--visibility=selected`

Usage:  gh secret set <secret-name> [flags]

...

Logs

N/A