For the "Attach to Issue" feature, only show repos the user is a member or collaborator of

[mickmister]

There is a digression between how the "Create Issue" and "Attach to Issue as Comment" features, in how they filter on which repos can be chosen, specifically when the plugin is not locked to an organization.

The "Create Issue" repos are scoped to repos that user is a member or collaborator of. The "Attach to Issue" repos display several public repos that the user has no affiliation with.

As discussed here, the user should only be able to use repos they are affiliated with. In order to accomplish this, we should have a repo select box to allow the user to select the repo first, then the issue selector should filter on that selected repo.

[hanzei]

I not sure if this is feasible with the GitHub API. /search/labels doesn't allow limiting the results by affliction.

One alterative way to implement this ticket is to check for every returned issue if the user can an affliction to the repo, but that seams like a lot of overhead.

I'm wondering if instead the flow should be changed to have the user first select a repo and then an issue of this repo.

[mickmister]

I'm wondering if instead the flow should be changed to have the user first select a repo and then an issue of this repo.

👍 Updated description to reflect this @hanzei

[DHaussermann]

@mickmister I've also noticed that the create modal will not limit the user to creating issue to a specific organization when the organization is locked on the plugin config.
cc @aaronrothschild this creates an inconsistency between create and attach even when the plugin is configured to only use 1 organization.

[mickmister]

@DHaussermann So it sounds like the attach functionality is working correctly in regards to scoping to an org. Do you mind creating an issue to adjust the create functionality to match this functionality?

[DHaussermann]

Created #285 to address the create issue as I realize now that this task is only for changes to attach.