In #158 the event and context arguments to the callback got combined into one.
The documentation was still referring to the event object, which is no longer present.
These instructions referred to a file `autoresponder.js` which does not exist (a) for a plugin in general, or (b) for the autoresponder plugin in particular. The plugin template repo contains a file named `index.js` to export the plugin module, and this naming scheme seems to have been adopted widely (e.g. autoresponder, stale plugins both use `index.js`).
* origin/master: (45 commits)
Fix lint errors
Upate tests to handle async callback
Update docs
Pass an authenticated client to context
Log unhandled rejections
Find private key if it is not set
add .js ext to files in bin/; closes#129
add PRIVATE_KEY_PATH env var support; closes#122
ensure "start" script runs from local directory
enable autodiscovery of plugins; closes#99
use function expressions in suite and test blocks
Update filename
Edits
fix formatting
Contents
Heroku docs
edits
Release v0.4.1.
Disable raven console alerts
Relax node version requirements
...
# Conflicts:
# docs/api.md
# lib/context.js
# lib/robot.js
# package.json
The loading preference is:
1. CLI flag
2. `PRIVATE_KEY`
3. `PRIVATE_KEY_PATH`
4. Find a `.pem` file in the current working dir
Changes:
- break out PK loading logic into module `lib/private-key.js`
- add more info to error messaging if probot fails to find a PK
- add tests
- add note to deployment docs
* origin/master: (27 commits)
Release v0.4.1.
Disable raven console alerts
Relax node version requirements
Release v0.4.0.
Update log for local server
Remove tunnel script
Move subdomain config
Update docs to use localtunnel
Add subdomain option
Setup tunnel using localtunnel
Ensure node version is satisfied
autoBreadcrumbs
Use local logger variable
Connect sentry to logger
Move logger setup to index
Fix package.json for multiple plugins
Specific filename not needed
Remove log
Ignore all private keys
Look for any pem in the cwd
...
