Skip to content
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

Merged
merged 7 commits into from
May 22, 2024
Merged

Conversation

ajhenry
Copy link
Contributor

@ajhenry ajhenry commented May 20, 2024

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

  • If documentation is needed for this change, has that been included in this pull request
  • run npm run lint and fix any linting issues that have been introduced
  • run npm run test and run tests

Reviewer

  • Label as either bug, documentation, enhancement, infrastructure, maintenance, or breaking

@ajhenry ajhenry requested a review from a team as a code owner May 20, 2024 21:02
@ajhenry ajhenry added the enhancement New feature or request label May 20, 2024
@ajhenry ajhenry changed the title Swap out smee with homegrow proxy client feat: swap out smee with homegrow proxy client May 20, 2024
@ajhenry ajhenry changed the title feat: swap out smee with homegrow proxy client feat: swap out smee with homegrown proxy client May 20, 2024
@zkoppert
Copy link
Contributor

Should this also be removed now? Looks like a dead code path if your not using smee any longer: probot-forwarder.js

package.json Show resolved Hide resolved
@ajhenry
Copy link
Contributor Author

ajhenry commented May 21, 2024

@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 😄

@sutterj
Copy link
Contributor

sutterj commented May 21, 2024

Pulled changes and tested locally. Works as expected.

package.json Outdated Show resolved Hide resolved
Copy link
Contributor

@zkoppert zkoppert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍🏻

@ajhenry ajhenry merged commit cd3e9a8 into main May 22, 2024
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Replace smee
3 participants