Usability: Repository is dirty doesn't really tell much about what's going on with the repo.

[cognivore]

Why?

In doma.dev, we're repeatedly spending a lot of time on debugging "repository is dirty" when GPG fucks something up and veil still proceeds to create a darcs change.

We need to go beyond just having an informative message, ideally, we want to find the bug in veil that causes the bug to happen where a GPG fuck-up doesn't get caught and the change is still added. But making sure that we're spending less time on debugging "repository is dirty" message is the first and foremost task.

How?

• Look at isDirty function's branches;
• Make custom messages depending on the branch.

[cognivore]

Function:

passveil/src/PassVeil/Store/Repository.hs

Line 27 in c588b35

isDirty :: Store -> IO Bool