From: Arran Cudbard-Bell <a.cudbardb@freeradius.org>
Date: Mon, 13 Jul 2015 14:46:30 +0000 (-0400)
Subject: Mention putting log output in backticks
X-Git-Tag: release_3_0_10~353
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=1d1848e82b25d1048b5c19a9b17341b05e731b58;p=thirdparty%2Ffreeradius-server.git

Mention putting log output in backticks
---

diff --git a/CONTRIBUTING b/CONTRIBUTING
index ac3bef33e87..0e478db69a1 100644
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -50,6 +50,10 @@
   See doc/bugs (https://github.com/FreeRADIUS/freeradius-server/blob/master/doc/bugs) for information
   on what to include, and how to obtain it.
 
+  When logging bug reports using the GitHub issue tracker, pay attention to formatting.  You should
+  ensure any log output is surrounded by two sets of tripple backticks (```).  If you don't do this
+  Github will automatically link your issue to other pre-existing issues when it encounters a #<num>
+  string.
 
 4.PULL REQUESTS AND CODING STANDARDS