瀏覽代碼

DevKit updates (#3974)

Sonata CI 9 年之前
父節點
當前提交
ad60f49baf
共有 3 個文件被更改,包括 10 次插入2 次删除
  1. 6 1
      .github/ISSUE_TEMPLATE.md
  2. 2 0
      .styleci.yml
  3. 2 1
      CONTRIBUTING.md

+ 6 - 1
.github/ISSUE_TEMPLATE.md

@@ -44,4 +44,9 @@ $ php -v
 
 
 ## Actual results
 ## Actual results
 
 
-<!-- If it's an error message or piece of code, use code block tags. -->
+<!--
+    If it's an error message or piece of code, use code block tags,
+    and make sure you provide the whole stack trace(s),
+    not just the first error message you can see.
+    More details here: https://github.com/sonata-project/SonataAdminBundle/blob/3.x/CONTRIBUTING.md#issues
+-->

+ 2 - 0
.styleci.yml

@@ -23,3 +23,5 @@ enabled:
 finder:
 finder:
   exclude:
   exclude:
     - 'Tests/Fixtures'
     - 'Tests/Fixtures'
+    # ecommerce special case:
+    - 'Resources/skeleton'

+ 2 - 1
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
 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
 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
 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
 * Screenshots should be considered additional data, and therefore, you should
   always provide a textual description of the bug. It is strongly recommended
   always provide a textual description of the bug. It is strongly recommended
 to provide them when reporting UI-related bugs.
 to provide them when reporting UI-related bugs.