Markdown Cleanup Github Bot: Difference between revisions
From charlesreid1
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
MCBot = Markdown Cleanup Github Bot | MCBot = Markdown Cleanup Github Bot | ||
==Notes== | |||
Here's how this thing works: | Here's how this thing works: | ||
| Line 13: | Line 15: | ||
* 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== | |||
Also see [[DIY CI]] | |||
Revision as of 19:27, 4 August 2018
MCBot = Markdown Cleanup Github Bot
Notes
Here's how this thing works:
- 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