]> git.ipfire.org Git - thirdparty/freeradius-server.git/commitdiff
Mention putting log output in backticks
authorArran Cudbard-Bell <a.cudbardb@freeradius.org>
Mon, 13 Jul 2015 14:46:30 +0000 (10:46 -0400)
committerArran Cudbard-Bell <a.cudbardb@freeradius.org>
Mon, 13 Jul 2015 14:46:36 +0000 (10:46 -0400)
CONTRIBUTING

index ac3bef33e87aadec84924d9bb51e53d982c5cf7f..0e478db69a1e231dda7ad882de17aacde1c66128 100644 (file)
   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