From b89d4268ae341c2579e5af6253a4735705659a04 Mon Sep 17 00:00:00 2001 From: Sonata CI Date: Sat, 25 Jun 2016 05:30:08 +0200 Subject: [PATCH] DevKit updates (#115) --- .github/ISSUE_TEMPLATE.md | 7 ++++++- .styleci.yml | 2 ++ CONTRIBUTING.md | 3 ++- 3 files changed, 10 insertions(+), 2 deletions(-) diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md index 1ebbe6ea..11601b37 100644 --- a/.github/ISSUE_TEMPLATE.md +++ b/.github/ISSUE_TEMPLATE.md @@ -44,4 +44,9 @@ $ php -v ## Actual results - + diff --git a/.styleci.yml b/.styleci.yml index 8e5c9db7..8b1384c4 100644 --- a/.styleci.yml +++ b/.styleci.yml @@ -23,3 +23,5 @@ enabled: finder: exclude: - 'Tests/Fixtures' + # ecommerce special case: + - 'Resources/skeleton' diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index da40fbdb..c6c1125d 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -34,7 +34,8 @@ Github by following these points are taken care of: end of the page. Just look for "Stack Trace (Plain Text)", and copy/paste what you see. **Do not** make a screenshot of the stack trace, as screenshots are not indexed by search engines and will make it difficult for other people to -find your bug report. +find your bug report. If you have an issue when using the Symfony CLI, +use the `-vvv` option to get a stack trace. * Screenshots should be considered additional data, and therefore, you should always provide a textual description of the bug. It is strongly recommended to provide them when reporting UI-related bugs.