Describe the feature or problem you’d like to solve
In the case of GHEC, due to company policy, repo visibility cannot be set to public for most repositories.
gh skill search allows users to search for skills belonging to a specific username or organization using the --owner parameter, even if the repository visibility setting is set to Internal.
However, there is no way to search for skills distributed by other org/usernames within the GHEC, and there are significant difficulties in sharing skills with other organizations within the same company.
However, providing a method to search for skills distributed by other org/usernames within the company is expected to be of great help in collaborating with other organizations within the same company.
Proposed solution
How about providing a feature to filter by including internal repo visibility, either by using the 'enterprise' name for the --owner parameter or by using a separate --enterprise parameter?
Describe the feature or problem you’d like to solve
In the case of GHEC, due to company policy, repo visibility cannot be set to public for most repositories.
gh skill searchallows users to search for skills belonging to a specific username or organization using the--ownerparameter, even if the repository visibility setting is set toInternal.However, there is no way to search for skills distributed by other org/usernames within the GHEC, and there are significant difficulties in sharing skills with other organizations within the same company.
However, providing a method to search for skills distributed by other org/usernames within the company is expected to be of great help in collaborating with other organizations within the same company.
Proposed solution
How about providing a feature to filter by including internal repo visibility, either by using the 'enterprise' name for the
--ownerparameter or by using a separate--enterpriseparameter?