-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: swap out smee with homegrown proxy client #124
Conversation
Should this also be removed now? Looks like a dead code path if your not using smee any longer: probot-forwarder.js |
@zkoppert Ah yea I was debating leaving the smee client in there in case there's a bug with this one but I now realize that's why we have version control 😄 |
Pulled changes and tested locally. Works as expected. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍🏻
Pull Request
Proposed Changes
This gets rid of smee as the preferred local webhook client. This does not require a webhook url anymore in the env but does require setting
PUBLIC_ORG
This fixes #100
Readiness Checklist
Author/Contributor
npm run lint
and fix any linting issues that have been introducednpm run test
and run testsReviewer
bug
,documentation
,enhancement
,infrastructure
,maintenance
, orbreaking