chore: add Wit.ai config and update server startup message (#126)#127
Open
pranavshar223 wants to merge 2 commits intoasyncapi:masterfrom
Open
chore: add Wit.ai config and update server startup message (#126)#127pranavshar223 wants to merge 2 commits intoasyncapi:masterfrom
pranavshar223 wants to merge 2 commits intoasyncapi:masterfrom
Conversation
pranavshar223
requested review from
AceTheCreator,
asyncapi-bot-eve,
derberg and
magicmatatjahu
as code owners
|
pranavshar223
changed the title
Author
|
I would like to contribute to the Chatbot project of AsyncAPI. Please review my PR when you get a chance. I have experience working on similar projects and would love to discuss the next steps. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
add the configure information about Wit.ai. That helps the new contribution to start the local servers.
and show the message at the console "Server running in production on port 5000"
solving the issue #126