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.
Add guide on creating issues to CONTRIBUTING.md
See original GitHub issueType of issue: bug report | feature request | documentation | other enhancement Documentation
Impact: no functional change | API addition (no impact on existing code) | API modification | unknown No functional change
Development Phase: request | proposal proposal Other information
If the current behavior is a bug, please provide the steps to reproduce the problem:
What is the current behavior? CONTRIBUTING.md has no guide on creating an issue What is the expected behavior? I think CONTRIBUTING.md should have a guide on creating a new issue. Please tell us about your environment:
What is the use case for changing the behavior?
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (11 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
Okay I’ve seen a documentation on from the learn more link.
Sure… our README also encourages people to use stack overflow and gitter. We want to discourage people from opening GitHub issues for user error “I can’t get it to work” type questions.