Go to file
Giancarlos Salas 70f4a041f6 refactor: user response.headers instead of deprecated response.meta (#550) 2018-05-31 13:22:26 -07:00
.github docs: Issue templates (#525) 2018-05-13 01:15:13 -04:00
bin chore: Rewrite core in Typescript (#372) 2018-05-25 15:17:19 -05:00
docs docs: deployment to now (#548) 2018-05-29 13:44:50 -07:00
script chore: Remove scripts that are no longer used (#468) 2018-03-18 18:03:45 -05:00
src refactor: user response.headers instead of deprecated response.meta (#550) 2018-05-31 13:22:26 -07:00
static chore: Add icon to title of probot (#483) 2018-04-05 13:59:44 -05:00
test chore: Rewrite core in Typescript (#372) 2018-05-25 15:17:19 -05:00
views chore: Add icon to title of probot (#483) 2018-04-05 13:59:44 -05:00
.editorconfig Add editorconfig 2016-09-16 11:45:59 -07:00
.gitignore chore: Rewrite core in Typescript (#372) 2018-05-25 15:17:19 -05:00
.jsdoc.json Update publish-docs to copy API docs to website 2017-08-18 10:55:11 -05:00
.travis.yml chore: Rewrite core in Typescript (#372) 2018-05-25 15:17:19 -05:00
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md 2017-04-06 18:49:20 -05:00
CONTRIBUTING.md docs: suggested changes from audit #522 (#523) 2018-05-13 01:16:43 -04:00
LICENSE docs: suggested changes from audit #522 (#523) 2018-05-13 01:16:43 -04:00
README.md Audit of readme based on maintainer audit feedback (#526) 2018-05-13 15:32:56 -05:00
app.json pro the bot 2017-08-29 23:38:51 -05:00
appveyor.yml chore: Setup Appveyor (#334) 2017-11-19 23:57:37 -05:00
codecov.yml chore: Disable codecov comments (#543) 2018-05-22 22:41:44 -07:00
package.json chore: Rewrite core in Typescript (#372) 2018-05-25 15:17:19 -05:00
tsconfig.json chore: Rewrite core in Typescript (#372) 2018-05-25 15:17:19 -05:00
tslint.json chore: Rewrite core in Typescript (#372) 2018-05-25 15:17:19 -05:00

README.md

Probot

npm version

🤖 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. 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 = robot => {
  robot.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!