* Add button to setup GitHub app * Add app.yml * Add some comments to app.yml * Associate events with permissions * Allow configuring app with manifest * Hacky version of callback URL for configuring app * Remove manifest stuff for now * Return nil if private key is not found * Move setup stuff to a separate plugin * Revert changes to default plugin * Remove FIXME * Revert changes to default template * Use separate template for setup * Fix lint warnings * Convert test helper to typescript * Initial test for setup app * Require tests files to match `.test.(js|ts)` * Account for multiple protocols in x-forwarded-proto * Wrap pem in quotes * Collapse class into request method for now * run `refresh` after updating .env on Glitch * Extract update-dotenv to a node module * Create a smee url if one does not exist * Hacky version of serving up the manifest * WIP Manifest with code * add comments for plan + figure out port * using user-agent header for review lab * add success view to redirect to after installation * api is actually on github * start making post * fix quoting issue on POST * everything is off review lab and on dotcom * working version of app manifest flow * Start trying to write tests against setup * more refactor into thingerator; basic tests; write plans for other tests * merge better.. * ok atom conflict handling broke * hack the tests back together * pass the tests 👊🏼 * moar test * make it open in a new tab for Wil 💖 * make boolean work * clean up logic, move messgae, just return html url not response * clean up tests 👷🏾♀️ * rename Brandon's thingerator to manifest-creation
Probot
🤖 A framework for building GitHub Apps to automate and improve your workflow
If you've ever thought, "wouldn't it be cool if GitHub could…"; I'm going to stop you right there. Most features can actually be added via GitHub Apps, which extend GitHub and can be installed directly on organizations and user accounts and granted access to specific repositories. They come with granular permissions and built-in webhooks. Apps are first class actors within GitHub.
How it works
Probot is a framework for building GitHub Apps in Node.js, written in TypeScript. GitHub Apps can listen to webhook events sent by a repository or organization. Probot uses its internal event emitter to perform actions based on those events. A simple Probot App might look like this:
module.exports = (app) => {
app.on('issues.opened', async context => {
const issueComment = context.issue({ body: 'Thanks for opening this issue!' })
return context.github.issues.createComment(issueComment)
})
}
Building a Probot App
If you've landed in this GitHub repository and are looking to start building your own Probot App, look no further than probot.github.io! The Probot website contains our extensive getting started documentation and will guide you through the set up process.
This repository hosts the code for the npm Probot package which is what all Probot Apps run on. Most folks who land in this repository are likely looking to get started building their own app.
Contributing
Probot is built by people just like you! Most of the interesting things are built with Probot, so consider starting by writing a new app or improving one of the existing ones.
If you're interested in contributing to Probot itself, check out our contributing docs to get started.
Want to chat with Probot users and contributors? Join us in Slack!
Ideas
Have an idea for a cool new GitHub App (built with Probot)? That's great! If you want feedback, help, or just to share it with the world you can do so by creating an issue in the probot/ideas repository!