From 943156d8794772c23a0a0f6e5120c40b8c7981ec Mon Sep 17 00:00:00 2001 From: Andrey Orst Date: Wed, 11 Apr 2018 22:55:30 +0300 Subject: [PATCH] Add note about contributing to traceback (#969) There too many issues with traceback only. While it is good to have traceback, it is sell useful when it is the only info in the issue description. I think that contributing manual should be mentioned here even if we have issue template now. At least further new issues with traceback may follow contributing guide. --- pythonx/UltiSnips/err_to_scratch_buffer.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/pythonx/UltiSnips/err_to_scratch_buffer.py b/pythonx/UltiSnips/err_to_scratch_buffer.py index daec4df..e82fa41 100644 --- a/pythonx/UltiSnips/err_to_scratch_buffer.py +++ b/pythonx/UltiSnips/err_to_scratch_buffer.py @@ -18,7 +18,9 @@ def wrap(func): msg = \ """An error occured. This is either a bug in UltiSnips or a bug in a snippet definition. If you think this is a bug, please report it to -https://github.com/SirVer/ultisnips/issues/new. +https://github.com/SirVer/ultisnips/issues/new +Please read and follow: +https://github.com/SirVer/ultisnips/blob/master/CONTRIBUTING.md#reproducing-bugs Following is the full stack trace: """