mattermost / mattermost/mattermost-plugin-github
For the "Attach to Issue" feature, only show repos the user is a member or collaborator of
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 179
- Forks
- 180
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 13
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the existing "Create Issue" and "Attach to Issue as Comment" flows, then review the discussion in pull request 239. Start by tracing how each flow loads and filters repositories. Done means the attach flow first offers only repositories where the user is a member or collaborator, and the issue selector is filtered by that repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100