Markdown Cleanup Github Bot: Difference between revisions
From charlesreid1
No edit summary |
(→Notes) |
||
| Line 3: | Line 3: | ||
==Notes== | ==Notes== | ||
Here's how this thing works: | ===The Theory== | ||
Here's how this thing works, in theory: | |||
* 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 15: | Line 17: | ||
* 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 | ||
==Related== | ==Related== | ||
Also see [[DIY CI]] | Also see [[DIY CI]] | ||
Revision as of 19:40, 4 August 2018
MCBot = Markdown Cleanup Github Bot
Notes
=The Theory
Here's how this thing works, in theory:
- 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.
Useful: PR request hook (flask server) that comments on PRs from first-time contributors
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
Related
Also see DIY CI