Clarify list repo behavior

[ncalteen]

This PR adds some clarification to the gh repo list command. Specifically, it addresses a possible point of confusion: when listing forks for an organization, it does not include forks owned by members of the organization.

Edit by @williammartin: This PR relates to #7975 and #7958

[cliAutomation]

Hi! Thanks for the pull request. Please ensure that this change is linked to an issue by mentioning an issue number in the description of the pull request. If this pull request would close the issue, please put the word 'Fixes' before the issue number somewhere in the pull request body. If this is a tiny change like fixing a typo, feel free to ignore this message.

[williammartin]

Thanks @ncalteen for your efforts to improve the CLI!.

I understand the change you have made but I think I'm missing some context on how you came to believe that that this command would show repositories owned by members of an organization, as they would not be "owned by an organization". Also, could write a little bit more about what you were trying to achieve, as maybe there is some useful enhancement we could add to the CLI, or another solution we could offer?

Also, as per our contributing guidelines we ask that PRs are created only for pre-approved work. Often there is more than one outcome for a solution and it helps us a lot to understand what our users are trying to do without muddying PRs with loosely related discussions.

Cheers!

[ncalteen]

Hi @williammartin apologies I missed that callout in the contribution guide! If you'd prefer then, I can close out this PR and move it to an issue. Just let me know.

In the meantime, the reason for this was a customer request. Their initial review of the documentation gave them the impression that this CLI action would list all forks within the organization when provided an org as the input.

[williammartin]

Their initial review of the documentation gave them the impression that this CLI action would list all forks within the organization when provided an org as the input.

So just to be sure I understand, their use case was wanting to know about any forks of any repos in their organization? I assume that only members of their organization could make forks?

I think this is an interesting enough use case to capture as its own discussion. Even if we don't end up supporting such a use case, it's useful discoverable context for anyone in the future.

[ncalteen]

Sounds good to me! I will move this discussion to an issue. Apologies again for not following the contribution guide correctly!

[williammartin]

Not a problem.

[cliAutomation]

Hi! Thanks for the pull request. Please ensure that this change is linked to an issue by mentioning an issue number in the description of the pull request. If this pull request would close the issue, please put the word 'Fixes' before the issue number somewhere in the pull request body. If this is a tiny change like fixing a typo, feel free to ignore this message.

[cliAutomation]

Hi! Thanks for the pull request. Please ensure that this change is linked to an issue by mentioning an issue number in the description of the pull request. If this pull request would close the issue, please put the word 'Fixes' before the issue number somewhere in the pull request body. If this is a tiny change like fixing a typo, feel free to ignore this message.

[williammartin]

LGTM.