From d93b6b2d9f3dbd3eb69ea1e3cae9d44c5650a4c2 Mon Sep 17 00:00:00 2001 From: Tim Guirgies Date: Wed, 25 May 2011 02:15:13 +1000 Subject: Remove "be set" reference in favour of actual help Because "be set severity blah" does not actually work, referring users there to set custom severity levels is just cruel (I spent a half hour trying to figure out what I was doing wrong). Thus, it is much easier to, at least for now, state in the help message what they must do in order to get custom severities and statuses. --- libbe/command/severity.py | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) (limited to 'libbe/command/severity.py') diff --git a/libbe/command/severity.py b/libbe/command/severity.py index c510bc4..3aea386 100644 --- a/libbe/command/severity.py +++ b/libbe/command/severity.py @@ -99,6 +99,18 @@ Severity levels are: %s You can overide the list of allowed severities on a per-repository basis. -See "be set --help" for more details. +In order to do so, you must edit your be settings file. This can be found within your .be/xxx-xxx directory. + +Add the following lines to override the default severities and use your own: + +severities: + - - target + - The issue is a target or milestone, not a bug. + - - wishlist + - A feature that could improve usefulness, but not a bug. + +You may add as many name/description pairs as you wish to have; they are sorted in order from least important at the top, to most important at the bottom. + +Note that the values here _override_ the defaults. That means that if you like the defaults, and wish to keep them, you will have to copy them here before adding any of your own. """ % ('\n '.join(severity_levels)) return ret -- cgit