Markdown Cleanup Github Bot: Difference between revisions
From charlesreid1
(→Notes) |
|||
| Line 3: | Line 3: | ||
==Notes== | ==Notes== | ||
=== | ===In Theory=== | ||
Here's how this thing works, in theory: | Here's how this thing works, in theory anyway: | ||
* First, you set up a Github bot account - the user that will do your bidding. | * First, you set up a Github bot account - the user that will do your bidding. | ||
| Line 11: | Line 11: | ||
* This is still totally unclear. | * This is still totally unclear. | ||
How it works: | How it works: | ||
* Run the flask app somewhere (self-hosted, heroku, google app engine) | * Run the flask app somewhere (self-hosted, heroku, google app engine) | ||
* Install a webhook in your repo that pings the endpoint, and only do on pull request events | * Install a webhook in your repo that pings the endpoint, and only do on pull request events | ||
Why I'm still confused: | |||
* The OAuth application has an "owner" and it has "users" | |||
* We're trying to build a bot that can comment on pull requests in private repositories | |||
* Does the OAuth application simply need to request write permission for repos? | |||
* Can the owner of the OAuth application then do what they'd like? Do the changes show up under the account of the OAuth application's owner? | |||
===Links=== | |||
Useful: PR request hook (flask server) that comments on PRs from first-time contributors | |||
* https://github.com/Deborah-Digges/pr-bot | |||
==Related== | ==Related== | ||
Also see [[DIY CI]] | Also see [[DIY CI]] | ||
Revision as of 19:44, 4 August 2018
MCBot = Markdown Cleanup Github Bot
Notes
In Theory
Here's how this thing works, in theory anyway:
- First, you set up a Github bot account - the user that will do your bidding.
- Next, you create a Github OAuth account as that user. This OAuth application will ask users for various permissions. One of those permissions is the ability to commit to repositories.
- This is still totally unclear.
How it works:
- Run the flask app somewhere (self-hosted, heroku, google app engine)
- Install a webhook in your repo that pings the endpoint, and only do on pull request events
Why I'm still confused:
- The OAuth application has an "owner" and it has "users"
- We're trying to build a bot that can comment on pull requests in private repositories
- Does the OAuth application simply need to request write permission for repos?
- Can the owner of the OAuth application then do what they'd like? Do the changes show up under the account of the OAuth application's owner?
Links
Useful: PR request hook (flask server) that comments on PRs from first-time contributors
Related
Also see DIY CI