Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Push new bot to github
See original GitHub issueDescription
There’s a re-write that the EddieHub is going to undergo. We could ensure the faster migration of old functionality to the new version if the current running bot’s code is pushed to this repo. Moreover, it would be great if we keep the old code in a new branch called archive or something
Moreover, the current bot isn’t doing much(except the Alexjs part)
Additional Context
ref: Following a discussion in discord
https://discord.com/channels/699608417039286293/738541096098988072/838889005986086923
https://discord.com/channels/699608417039286293/738541096098988072/838894715571011584
Summary:
*If we’re re-working the EddieHubCommunity/EddieBot project(Imo we could maybe re-use some of the old code in the new version to add some essential functionalities, like the ^support command)
Eddie- You are right, we need to be clear. I think we should keep stargate as it and push to EddieBot 👍 - we can then slowly migrate features to the new deployed EddieBot
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This is done now, I believe. Feel free to reopen if I’m wrong.
closed by https://github.com/EddieHubCommunity/EddieBot/commit/5c4b51b0774cbe5c6c4a1da3bfa09f266a6503ca https://github.com/EddieHubCommunity/EddieBot/commit/5c4b51b0774cbe5c6c4a1da3bfa09f266a6503ca