fix(lambda): Delete lambda implementation #381
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I wanted to use Google Lambda function as a server-less solution for the bot initially. FOr some reason the answer latency was off the charts so I got back to the classic server way. If I to implement it again, most likely I would need to start from scratch. So no good reason to keep it in the code base. I can always recover the git history
n0th1ng-else
force-pushed
the
remove-lambda
branch
from
c6c8bf5
to
e34fb6e
Compare
|
|
🎉 This PR is included in version 4.27.3 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I wanted to use Google Lambda function as a server-less solution for the bot initially.
FOr some reason the answer latency was off the charts so I got back to the classic server way.
If I to implement it again, most likely I would need to start from scratch. So no good reason to
keep it in the code base. I can always recover the git history