Design of initial version.

[ffranr]

This issue outlines the design of the very first basic direction of development. In future work, the following commands may well be extended beyond what is proposed here.

Status Command

git crev status

Prints out the total number of commits reviewed and un-reviewed for the current working directory git repo. Indicates whether a review is ongoing.

Review Commands

Add commits to a review

git crev add <git revision range>

Initiates the construction of a review (if none is currently ongoing). Adds the commits in <git revision range> to the review. Default revision range is HEAD.

Remove commits from a review

git crev remove <git revision range>

Removes the commits in <git revision range> from an ongoing review. Default revision range is HEAD.

Clear current review

git crev clear

Remove all commits from an ongoing review.

Commit and sign the review

git crev commit

Sign an ongoing review and thereby create a proof. Ends an ongoing review.

[ffranr]

@dpc What do you think about this sort of direction?

[dpc]

Personally, I'm not a big fan of stateful CLI UIs and it shows in cargo crev. git UI is very stateful though. Combining git + crev is going to be inconsistent with one or the other. 😆 But git UI is so inconsistent that no one is going to mind anyway... 😆

I guess trying to appeal to git users makes sense. But I don't see the overreaching idea here. I would expect ... add <range> and ... commit or something like that?

[dpc]

One way or another, I would just dive into implementing what you want, and try to collect feedback from more people once there's something more material to work with. :)

[ffranr]

That makes sense! I've updated the design, but now I'm just going to just work on an implementation.