use CIL::Issue;
use CIL::Comment;
use CIL::Attachment;
+use CIL::Utils;
## ----------------------------------------------------------------------------
# constants
my( $command ) = grep { $command_name eq $_->name } CIL->commands
or Getopt::Mixed::abortMsg("'$command_name' is not a valid cil command.");
+ # make a new $cil object
my $cil = CIL->new();
+
+ # for all commands (except init), we need to know we can see the proper paths
+ # (ie. issues/)
+ CIL::Utils->check_paths( $cil )
+ unless $command_name eq 'init';
+
$cil->read_config_user();
$cil->read_config_file();
$cil->check_args($args);
Summary: can't find issues folder
-Status: New
+Status: Cancelled
CreatedBy: Name <me@example.com>
AssignedTo:
Label: Milestone-v0.06
Inserted: 2009-06-06T09:39:09
-Updated: 2010-01-21T22:59:19
+Updated: 2010-01-21T23:12:50
Description ...
I created an issue, while in the issues folder.. it doesn't write it
Summary: cil add should detect early on if cil init hasn't been run
-Status: New
+Status: Finished
CreatedBy: Andrew Ruthven <andrew@etc.gen.nz>
AssignedTo:
Label: Milestone-v0.06
Inserted: 2008-09-22T03:26:21
-Updated: 2010-01-21T22:59:19
+Updated: 2010-01-21T23:11:51
Currently if you run cil add you can start to create a bug report, hit save
and then cil bombs out not being able to create a file inside issues.
$data->{$key} = $value;
}
}
-
+
# now read everything that's left into the $last_field field (if there is one)
$data->{$last_field} = join("\n", @lines)
if defined $last_field;