The existing format for commit logs will remain the default, but
this change allows customization of the `--date=format:` and
`--pretty=format:` arguments passed to `git log`. For example, I
prefer having the time of day a commit was made, and having the
time in front, which can now be done with these options:
```
git:
dateFormat: "%H:%M %d %b %y"
commitFormat: "[forestgreen]%h [grey]%cd [white]%s [grey]%an[white]"
```
(sorry, this doesn't update documentation - if you let me know
what files to edit for those and how to "build" the docs to update
them, I can try to do that better in future changes)
After setting up the git module with multiple repos and switching
between them, I observed some graphical wonkiness in the display:
https://i.imgur.com/R3e7eij.png
After adding some log statements, I tracked it down to the
`GitRepo.Repository` field having a newline in it after it's set
from a command execution's stdout. This change strips the
repository path of spaces when assigning to the `Repository` field,
which fixes the display issues.
For my own use case (and anyone in a similar situation), the Jira
module is more useful if I can specify a list of projects to
display issues from, rather than no project (which selects all
projects) or one specific project.
New supported syntax:
` project: ["PROJA", "PROJB"]`
If this is merged, documentation for the Jira module should be
updated accordingly. (Sorry, I would have done this myself but
I'm not sure what the right place is - when grepping I find
multiple places in the repo containing documentation strings
and I'm not sure what the "master" location is)
Specifying a single project (or no project) is still supported -
behavior shouldn't change for anyone who doesn't change their
config.