David E. Wheeler
David E. Wheeler
There is a lot of common code in `Command::log` and `Command::plan`. Refactor it out into a role, named App::Sqitch::Role::SearchCommand, perhaps.
Add a `-d` and `--delete` option to the `tag` command to delete a tag. Refuse to remove the tag if it is used for the suffix for any reworked changes...
With this option on, missing verify scripts will be considered failures, rather than just warn. Probably should have it on `deploy` and `rebase`, too.
If, for example, you wanted to run verify scripts through `pg_prove` instead of `psql`, you could set it up with something like: ``` sqitch config verify.client 'pg_prove -U %u -h...
The error codes for `git config` are very useful. Some of them are duplicated in `sqitch command`, but not all. It could use a bit more work to get them...
Similar to how they work for the `log` command. Maybe. If anyone really cares.
- Allow searching by dates. Would probably have to use [DateTime::Format::Flexible](https://metacpan.org/module/DateTime::Format::Flexible) or similar to parse user-specified DateTime formats. - Allow searching of email addresses. Right now, the `--committer` and `--planner`...
Need a command to change dependencies. Maybe `sqitch revise`? Too close to `rework`? Maybe just `sqitch require $change $dep` and `sqitch conflict $change $dep`?
Not sure what to call it, but the idea is to be able to convert an existing project over to using Sqitch by writing a plan from the VCS history.
If a change is deployed to a database, but then later tagged, there needs to be a way to apply that tag to the existing named change in the database....