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.
$ probot console
See original GitHub issueI used to use script/console a lot to experiment with GitHub API calls. I stoped using it over time, primarily because Probot switched away from using a bot token to use GitHub Apps and there were often APIs that would work with a token and then not work for GitHub Apps.
It’d be cool to add $ probot console as a command you could run from any Probot app that would give you an interactive node console with some stuff pre-wired, including an authenticated client to test out API calls.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:5 (3 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
Wait a minute, @stale. I like this idea.
This is a great idea - in my todo app, I have a CLI script that calls the app code with a fake event (but on potentially real data), and stubs out the relevant GitHub client methods to write to
stdoutinstead of actually making POST requests. It’s obviously very tailored to what I need in an event, so I’m just sharing it as a little bit of prior art.