mattermost / mattermost/mattermost-plugin-github
Document behavior for org-level setup and user access control
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 179
- Forks
- 180
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 13
Description
Comment from discussion on community. Please see the whole thread for more context:
After further testing, it seems like location of the oauth app doesn't matter, and the user running /github connect doesn't need to be a member of that org. The user's github access controls which repos they can subscribe a channel to, but the subscriptions persist to that channel regardless of the user's continued access. Is that correct?
Issue created from a Mattermost message by @jmastron.
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
Read the linked Mattermost community thread and investigate the /github connect flow. Confirm the behavior around OAuth app location, organization membership, repository access, and persistent channel subscriptions. Done means the verified behavior and access-control rules are documented clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- authorization, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100