Imported Upstream version v0.3.0upstream/v0.3.0

1 files changed, 19 insertions, 1 deletions

diff --git a/README b/README
index 607b470..c0f3d5e 100644
--- a/README
+++ b/README
@@ -32,15 +32,27 @@ list all the issues by using the 'list' command:
 
  $ cil list
 
+When listing the issues, they can also be filtered:
+
+ $ cil list --status=New
+ $ cil list --label=Type-Enhancement
+ $ cil list --is-open
+ $ cil list --label=Milestone-v0.3 --is-open
+
 You can see what the issue name is by looking at the 'Issue' title. Imagine it
 is 'cafebabe' (which by default is the time from epoch). To see your issue
 again, use the 'show' command:
 
  $ cil show cafebabe
 
-Another reporting command is 'summary':
+Another reporting command is 'summary' for which all the filter options also
+apply:
 
  $ cil summary
+ $ cil summary --status=New
+ $ cil summary --label=Type-Enhancement
+ $ cil summary --is-open
+ $ cil summary --label=Milestone-v0.3 --is-open
 
 The columns show 'Name', 'Status', 'CreatedBy' and 'Summary'.
 
@@ -69,6 +81,12 @@ it from the issue:
 
  $ cil extract decaf7ea --filename=mycore
 
+Finally, because the cil issue files reside on the filesystem in flat files,
+there needs to be a way to check the integrity of the issues, therefore you can
+run this to do checks regarding the whole issue list:
+
+ $ cil fsck
+
 That's it for now. As you can see, if you've played with any kind of bug/issue
 tracker before, 'cil' is straightforward.