I’m planning a new web application that will enable Github users to improve the way they work with repositories and branches.
I’m not really clear though on whether I should design this as an OAuth app or Github app, I have read the documentation but still have questions.
The app must support the following
- Expose controls which are restricted by the user’s own Github account settings.
- Receive webhook events.
- Support organization as well as user/repo specificity.
So I want an org-admin (when using the new app) to be able to perform actions that are only allowed because they are an org admin.
Non-admin users won’t be able to perform actions disallowed by their org membership restrictions.
For example user’s of the app may get the ability to create a pull-request or may get the ability to merge a pull request, which of these they can do is to be wholly dictated by their Github userid and its defined limitations.
Is this best built as a “Github app” or a “OAuth app”?
Are there ways to “make the app look” like it is part of Github - to the user using it?
I guess the app is a kind if project management assistant if that helps to convey what I’m doing.
Any info is much appreciated.