--- /dev/null
+Issue: a90ad11f
+CreatedBy: Andrew Chilton <andychilton@gmail.com>
+Inserted: 2008-07-02T12:40:07
+Updated: 2008-07-02T12:42:18
+
+Nigel suggested on IRC of using the example .cil file in the manpage if wanting a default file:
+
+ StatusStrict: 1
+ StatusAllowedList: New
+ StatusAllowedList: InProgress
+ StatusAllowedList: Finished
+ StatusOpenList: New
+ StatusOpenList: InProgress
+ StatusClosedList: Finished
+ LabelStrict: 1
+ LabelAllowedList: Type-Enhancement
+ LabelAllowedList: Type-Defect
+ LabelAllowedList: Priority-High
+ LabelAllowedList: Priority-Medium
+ LabelAllowedList: Priority-Low
+
+Maybe a 'DefaultAssignedTo' in the .cil file might help.
Summary: Write a default .cil file so --commands work
Status: New
CreatedBy: Nigel McNie <nigel@mcnie.name>
-AssignedTo: Nigel McNie <nigel@mcnie.name>
+AssignedTo: Andrew Chilton <andychilton@gmail.com>
+Comment: d6ee2369
Inserted: 2008-07-02T12:22:45
-Updated: 2008-07-02T12:24:24
+Updated: 2008-07-02T12:42:18
When I tried to use cil for the first time, I did:
cil add
cil list --is-open
-And got no results. Because cil didn't know at that point what statuses counted as 'open'.
+And got no results. Because cil didn't know at that point what statuses counted
+as 'open'.
-It would be nice if a default .cil was written out, with just enough statuses etc. in it to make those common --command flags work.
+It would be nice if a default .cil was written out, with just enough statuses
+etc. in it to make those common --command flags work.
You could also add cil init --bare to not write this out.