$ did --gerrit-reviewed --since 2016-05-15 --debug
...
DEBUG chg = {u'status': u'MERGED', u'deletions': 8, u'updated': u'2016-05-16 11:52:24.552000000', u'insertions': 18, u'created': u'2016-02-16 13:33:33.000000000', u'change_id': u'Ie04d9f3e6948079c9c6918867cd670c636c61504', u'hashtags': [], u'project': u'XXXX', u'branch': u'master', u'owner': {u'_account_id': 1947}, u'_number': 67763, u'id': u'XXX', u'subject': u"XXXX"}
...

In plugin is check for 'author' and 'email', otherwise the record is skipped.
Which (at least for our internal gerrit) look to be omitted.

would you look in to including some functionality like this? https://github.com/ghelleks/pbureport

RedHat bugzilla tracks several components. I have some work done on Fedora and some on RHEL.

But when I run "did last week" I get list of bugs with their titles so it is hard to find out which are for Fedora and which for RHEL. Also info which product (aka package name) it was assigned to would be useful to have.

comparing to status-report, bugzilla plugin misses acked bugs.
There are more missing features like sanityonly or grading which are not part of this request.
version: copr did-0.9-1.fc23.noarch
did:

Bugzilla stats:
  --bugzilla-filed      Bugs filed
  --bugzilla-patched    Bugs patched
  --bugzilla-posted     Bugs posted
  --bugzilla-fixed      Bugs fixed
  --bugzilla-returned   Bugs returned
  --bugzilla-verified   Bugs verified
  --bugzilla-commented  Bugs commented
  --bugzilla-closed     Bugs closed
  --bugzilla            All above

status-report:

  Bugzilla stats:
    --verified          Bugs verified
    --sanity            SanityOnly bugs
    --returned          Bugs returned
    --filed             Bugs filed
    --fixed             Bugs fixed
    --posted            Bugs posted
    --patches           Patches written
    --acked             Bugs acked
    --graded            Bugs graded
    --commented         Bugs commented
    --bugzilla          All above

• Track bug creation, closure, assignment, comments, changes etc.
• Track karma

It seems that the gerrit plugin completely ignores the --until option. It should not :-)

did focuses on pulling data from external sources about things that a user 'did' during a time period.

Many times we 'do' things that aren't stored in any external source though, and thus can't be queried later and included into our reports. eg 'drafted really important slides in libraoffice for project X'

Users should be able to save (aka, cache) this type of arbitrary 'did' stat locally.

We should clearly warn when user (e.g. by a copy & paste accident)
specifies --since or --until options together with relative
time specification such as last week as it's not clear what the
desired result should be. Refusing to guess and suggesting to the
user to choose seems to be the most straightforward solution.

[DEBUG] url = https://gerrit.ovirt.org/changes/I9348a09e331195695c16862ef986df3b4abfa991/detail#/
[DEBUG] changelog = {u'status': u'NEW', u'topic': u'tc-tests', u'updated': u'2015-09-21 09:45:34.676000000', u'insertions': 49, u'messages': [{u'date': u'2015-09-21 08:58:42.371000000', u'_revision_number': 1, u'message': u'Uploaded patch set 1.', u'id': u'499865f5_1706631f', u'author': {u'username': u'ibarkan', u'email': u'[email protected]', u'name': u'Ido Barkan', u'_account_id': 1000618}}, {u'date': u'2015-09-21 08:58:59.549000000', u'_revision_number': 1, u'message': u"Patch Set 1:\n\n* Update tracker::IGNORE, no Bug-Url found\n* Check Bug-Url::WARN, no bug url found, make sure header matches 'Bug-Url: ' and is a valid url.\n* Check merged to previous::IGNORE, Not in stable branch (['ovirt-3.5', 'ovirt-3.4', 'ovirt-3.3'])", u'id': u'499865f5_171f4359', u'author': {u'username': u'gerrit-hooks', u'email': u'[email protected]', u'name': u'gerrit-hooks', u'_account_id': 1000458}}, {u'date': u'2015-09-21 09:40:59.984000000', u'_revision_number': 1, u'message': u'Patch Set 1:\n\nBuild Started -> http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc22-x86_64/687/', u'id': u'499865f5_97519363', u'author': {u'username': u'jenkins', u'name': u'Jenkins CI', u'_account_id': 1000132}}, {u'date': u'2015-09-21 09:45:34.676000000', u'_revision_number': 1, u'message': u'Patch Set 1: Continuous-Integration-1\n\nBuild Failed \n\nhttp://jenkins.ovirt.org/job/vdsm_master_check-patch-fc22-x86_64/687/ : FAILURE', u'id': u'499865f5_77d5e7b4', u'author': {u'username': u'jenkins', u'name': u'Jenkins CI', u'_account_id': 1000132}}], u'created': u'2015-09-21 08:58:42.371000000', u'change_id': u'I9348a09e331195695c16862ef986df3b4abfa991', u'labels': {u'Continuous-Integration': {u'default_value': 0, u'all': [{u'username': u'osvoboda', u'name': u'Ond\u0159ej Svoboda', u'_account_id': 1000529, u'value': 0, u'date': u'2015-09-21 09:07:09.728000000', u'email': u'[email protected]'}, {u'date': u'2015-09-21 09:45:34.676000000', u'username': u'jenkins', u'name': u'Jenkins CI', u'value': -1, u'_account_id': 1000132}, {u'username': u'gerrit-hooks', u'email': u'[email protected]', u'name': u'gerrit-hooks', u'value': 0, u'_account_id': 1000458}, {u'username': u'phoracek', u'name': u'Petr Hor\xe1\u010dek', u'_account_id': 1000595, u'value': 0, u'date': u'2015-09-21 09:07:07.137000000', u'email': u'[email protected]'}], u'values': {u' 0': u'Did not run yet', u'-1': u'Failed CI tests', u'+1': u'Passed CI tests'}, u'rejected': {u'username': u'jenkins', u'name': u'Jenkins CI', u'_account_id': 1000132}}, u'Verified': {u'default_value': 0, u'all': [{u'username': u'osvoboda', u'email': u'[email protected]', u'name': u'Ond\u0159ej Svoboda', u'value': 0, u'_account_id': 1000529}, {u'username': u'jenkins', u'name': u'Jenkins CI', u'value': 0, u'_account_id': 1000132}, {u'username': u'gerrit-hooks', u'name': u'gerrit-hooks', u'_account_id': 1000458, u'value': 0, u'date': u'2015-09-21 08:58:59.549000000', u'email': u'[email protected]'}, {u'username': u'phoracek', u'email': u'[email protected]', u'name': u'Petr Hor\xe1\u010dek', u'value': 0, u'_account_id': 1000595}], u'values': {u' 0': u'No score', u'-1': u'Fails', u'+1': u'Verified'}}, u'Code-Review': {u'default_value': 0, u'all': [{u'username': u'osvoboda', u'email': u'[email protected]', u'name': u'Ond\u0159ej Svoboda', u'value': 0, u'_account_id': 1000529}, {u'username': u'jenkins', u'name': u'Jenkins CI', u'value': 0, u'_account_id': 1000132}, {u'username': u'gerrit-hooks', u'email': u'[email protected]', u'name': u'gerrit-hooks', u'value': 0, u'_account_id': 1000458}, {u'username': u'phoracek', u'email': u'[email protected]', u'name': u'Petr Hor\xe1\u010dek', u'value': 0, u'_account_id': 1000595}], u'values': {u'+2': u'Looks good to me, approved', u' 0': u'No score', u'-1': u"I would prefer that you didn't submit this", u'+1': u'Looks good to me, but someone else must approve', u'-2': u'Do not submit'}}}, u'deletions': 2, u'project': u'vdsm', u'owner': {u'username': u'ibarkan', u'email': u'[email protected]', u'name': u'Ido Barkan', u'_account_id': 1000618}, u'permitted_labels': {}, u'mergeable': False, u'branch': u'master', u'removable_reviewers': [], u'_sortkey': u'0037f3890000b571', u'_number': 46449, u'id': u'vdsmmasterI9348a09e331195695c16862ef986df3b4abfa991', u'subject': u'net: tests: test tc upper limit using iperf'}
[DEBUG] changes.messages = [{u'_revision_number': 1,
u'author': {u'_account_id': 1000618,
u'email': u'[email protected]',
u'name': u'Ido Barkan',
u'username': u'ibarkan'},
u'date': u'2015-09-21 08:58:42.371000000',
u'id': u'499865f5_1706631f',
u'message': u'Uploaded patch set 1.'},
{u'_revision_number': 1,
u'author': {u'_account_id': 1000458,
u'email': u'[email protected]',
u'name': u'gerrit-hooks',
u'username': u'gerrit-hooks'},
u'date': u'2015-09-21 08:58:59.549000000',
u'id': u'499865f5_171f4359',
u'message': u"Patch Set 1:\n\n* Update tracker::IGNORE, no Bug-Url found\n* Check Bug-Url::WARN, no bug url found, make sure header matches 'Bug-Url: ' and is a valid url.\n* Check merged to previous::IGNORE, Not in stable branch (['ovirt-3.5', 'ovirt-3.4', 'ovirt-3.3'])"},
{u'_revision_number': 1,
u'author': {u'_account_id': 1000132,
u'name': u'Jenkins CI',
u'username': u'jenkins'},
u'date': u'2015-09-21 09:40:59.984000000',
u'id': u'499865f5_97519363',
u'message': u'Patch Set 1:\n\nBuild Started -> http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc22-x86_64/687/'},
{u'_revision_number': 1,
u'author': {u'_account_id': 1000132,
u'name': u'Jenkins CI',
u'username': u'jenkins'},
u'date': u'2015-09-21 09:45:34.676000000',
u'id': u'499865f5_77d5e7b4',
u'message': u'Patch Set 1: Continuous-Integration-1\n\nBuild Failed \n\nhttp://jenkins.ovirt.org/job/vdsm_master_check-patch-fc22-x86_64/687/ : FAILURE'}]
Traceback (most recent call last):
File "/home/ibarkan/pycharm-community-4.5.3/helpers/pydev/pydevd.py", line 2358, in
globals = debugger.run(setup['file'], None, None, is_module)
File "/home/ibarkan/pycharm-community-4.5.3/helpers/pydev/pydevd.py", line 1778, in run
pydev_imports.execfile(file, globals, locals) # execute the script
File "/usr/bin/did", line 36, in
did.cli.main()
File "/usr/lib/python2.7/site-packages/did/cli.py", line 183, in main
user_stats.check()
File "/usr/lib/python2.7/site-packages/did/stats.py", line 135, in check
stat.check()
File "/usr/lib/python2.7/site-packages/did/stats.py", line 135, in check
stat.check()
File "/usr/lib/python2.7/site-packages/did/stats.py", line 80, in check
self.fetch()
File "/usr/lib/python2.7/site-packages/did/plugins/gerrit.py", line 277, in fetch
if 'author' in chg and owner == chg['author']['email'] and
KeyError: 'email'

While sending PR #35 which allowed connecting to issues.jboss.org, I didn't realize that jboss.org is not connected to Red Hat LDAP :). So while the jira plugin started to work for jboss.org, I wasn't actually authenticated and that prevents me from monitoring internal Red Hat projects.

It seems the only way to authenticate to jboss.org is via basic authentication (?)

I suggest defining following new properties for jira plugin:

• auth_type - 'gss' (default) or 'basic'
• auth_url - instead of sso_url to make it more general
• auth_username, auth_password - for defining credentials, only possible for 'basic' auth. type

I'm willing to work on this.

@psss

Ultimately, while it's not perfect, I think it's going to be better if we have a readme file and man file that are separate from each other.

In 0.4 I've made a static cut of the man page; i don't think the man page will need to be updated very often. And once we have full docs... man page is just one more file out of many that we're going to need to make sure is accurate each time. It should be as simple as possible anyway, so hopefully even it won't need to be updated. In 0.4 the man pages are produced now using sphinx. The RPM makefile has been updated to build using sphinx. HTML output of the documentation is also using sphinx and is automatically regenerated over at status-report.readthedocs.org after each commit (you'll need to enable that in github repo hooks). Until you enable that hook i'm just manually re-generating the docs after commits though with a simple curl command::

curl -X POST http://readthedocs.org/build/status-report

See for example:
http://status-report.readthedocs.org/en/0.4/overview.html

See 7647e82

I've added git commit hooks too so now stuff can be checked automatically prior to making the commit. You need to enable it to work though:

# UPDATE according to your actual abs_path to this repo
PATH = ~/status-report/git-hooks
ln -s $(PATH)/pre-commit.py .git/hooks/pre-commit
ln -s $(PATH)/commit-msg.py .git/hooks/commit-msg

Currently enabled are commit-msg check (<= 50c) and pre-commit checks (RPM build and py.test)

I'd like to request support for a new plugin for the Redmine issue tracker:

http://www.redmine.org/

Thanks, did is very cool!

If commit message contain some special Unicode symbol (for example ' symbol) exception is thrown and it is not possible to create report.

did run with --debug option:

Traceback (most recent call last):
File "/usr/bin/did", line 36, in
did.cli.main()
File "/usr/lib/python2.7/site-packages/did/cli.py", line 191, in main
user_stats.check()
File "/usr/lib/python2.7/site-packages/did/stats.py", line 135, in check
stat.check()
File "/usr/lib/python2.7/site-packages/did/stats.py", line 135, in check
stat.check()
File "/usr/lib/python2.7/site-packages/did/stats.py", line 89, in check
self.show()
File "/usr/lib/python2.7/site-packages/did/stats.py", line 103, in show
utils.item(stat, level=1, options=self.options)
File "/usr/lib/python2.7/site-packages/did/utils.py", line 76, in item
eprint(u"{0}* {1}".format(u" " * indent, shorted(unicode(text), width)))
File "/usr/lib/python2.7/site-packages/did/plugins/github.py", line 86, in unicode
unicode(self.id).zfill(PADDING), self.data["title"])
UnicodeEncodeError: 'ascii' codec can't encode character u'\u2019' in position 36: ordinal not in range(128)

Problem git commit message is:

GUVNOR-2415: Boundary events lose it’s documentation after save and reopen Business Process

According to:
https://developer.github.com/v3/issues/

Note: In the past, pull requests and issues were more closely aligned than they are now. As far as the API is concerned, every pull request is an issue, but not every issue is a pull request.

This endpoint may also return pull requests in the response. If an issue is a pull request, the object will include a pull_request key.

enable support for grepping work done on JIRA tickets

The PatchedBugs class should return all the Bugzilla bugs to which the Patch keyword was added by given user in the specified date range. It works fine when Patch is the only keyword being added at a time. When adding other keywords at the same time, however, the bug is not listed in the report.

The problem is caused by the Bugzilla query used in the respective class, namely the following part:

class PatchedBugs(Stats):
    ...
    def fetch(self):
        ...
        query = {
            ...
            # Patch keyword added
            "field0-1-0": "keywords",
            "type0-1-0": "changedto",
            "value0-1-0": "Patch",
            ...
            }

In order to fix this behaviour, this needs to be modified to something like 'keywords changed to something which contains (not is) Patch'. From a quick look on Bugzilla search page, I am not quite sure at the moment how to define such a query, though.

When an email of non-existent user is provided searching for gerrit changes results in a traceback. This should probably just raise a warning or silently ignore this particular error. Otherwise it's not possible to create team reports with only some users having account on the gerrit instance.

Unfortunately it seems the only way how to detect the problem by checking the 400 error code from the server, no further details. So ignoring this could hide other problems as well. Not sure what's the best solution here.

Hi,
I just read documentation and have not found how to get status report for github projects, fedorahosted trac. For JIRA can you please add example, how to write it in config file?
Please add support for fedorahosted trac ticket status.

It would be nice to have an easy way to send/email the gathered
report directly from command line, optionally with editing it:

• After report is generated the content is open in $EDITOR
• When the content is empty, no email is sent (as git commit)
• Otherwise an email is sent based on the user config

Command line examples:

status-report --edit .......... just edit & print on stdout
status-report --send .......... send directly
status-report --send --edit ... edit & then send

Config example:

[email]
subject = [Status Report] Week $week
from = Petr Šplíchal <[email protected]>
to = Some Manager <[email protected]>
cc = Petr Šplíchal <[email protected]>

That's it! :-)

Hi.
It's nice to have the source code documented, but what I am really missing is some simple manual for newbies.

For example, I cannot find any explanation of the concept of section names - there are tons of example configs, but no single mention how do you choose the section names, or where are they used later.

Another example, I was interested what does this "prefix = BZ" option mean. It doesn't seem to be explained in the 'Config' chapter - instead it refers to 'Plugins' documentation. OK, so I went to Plugins/bugzilla and see this option repeated in config example snippet, but cannot find any single instance of 'prefix' within the explanatory text!

On the other hand, some other text, like "What did you do last week, month, year?" or "The config file ~/.did/config is used ..." is copied in multiple places.

Please, pretty please with sugar on top, take someone with zero knowledge of did and python, and write the manual from scratch while trying to teach the person how to use did ... do you really think that text like "class did.plugins.bugzilla.BugzillaStats(option, name=None, parent=None, user=None)" should be presented to users? Does your car manual list transponder chip model used in the remote while leaving out which button to press to open the car?

Would be useful for me if I could get status report details for my email usage.

Emails Sent (new, reply) - date: subject (like git commits)

Starting with support for gmail using their api would probably be reasonable.

I'll work on this.

review the updates to the latest plugins and double check that all the stuff is covered, even the updates to docs to include the plugin in the docs and the plugin sort order docs, etc.

It'd be cool to be able to query changes done to Errata Tool. I have some scripts which are able to access the tool, please ping me offline if interested. Unfortunately I don't have the time to work on this now;-/

Enable connecting user name resolution db. For example, email to full name. Could be simple RPC connector or LDAP or db

It would be nice to have plain user/password authentication support in the rt plugin as well. This could also allow us to create better test coverage for this plugin. Some useful links:

• https://issues.bestpractical.com/
• https://demo.bestpractical.com/
• http://requesttracker.wikia.com/wiki/REST#Python

The only thing I don't like about status-report is its name.
It's just too long and complicated to write on command line.
What about choosing something more comfortable and beautiful?

Commit d4cdbd2 shows how this could look like...
Usage like did last week seems quite natural ;-)

I use idonethis as a service for conveniently storing 'did's with a simple email each day (or at whatever other frequency); this allows me to quickly take notes about important things I've done from any device that supports email and (eg) easily share those with my team (who are also using idonethis). I'd like to continue to be able to use this service going forward, since a idid 'server' isn't likely anytime soon. But i'd like to keep a 'master' copy of all my stuff locally too that I can then

idid push TOPIC idonethis
idid pull idonethis TOPIC

or with config to the push to happen automatically (havn't thought about it deeply though)

[idonethis-kejbaly2]
token = ...

[joy]
type = logg
remote = idonethis-kejbaly2

idid joy 'something amazing today #ftw'
# this command would store the logg locally and also push it to idonethis 
# using the configured credentials

time spent emailing is also 'getting stuff done'; gmail should have an API that would enable users to query for how many messages sent, received, "read". This would be a good start.

I am not terribly familiar with setuptools but, shouldn't:
python-kerberos
python-nitrate
python-dateutil

be addressed in there? vs just the rpm spec?

For instance by adding "--urls" switch. The output would be:

* Bugs posted: 1
    * BZ#1268225 - [QE] (6.4.z) ReliableServiceWithRMTxStoreTestCase and...
       * https://bugzilla.redhat.com/show_bug.cgi?id=1268225

Getting this error when trying to connect to JIRA.

DEBUG Connecting to https://xxxx.xxxx..xxxx.com/step-auth-gss
Traceback (most recent call last):
File "/usr/bin/did", line 36, in
did.cli.main()
File "/usr/lib/python2.7/site-packages/did/cli.py", line 191, in main
user_stats.check()
File "/usr/lib/python2.7/site-packages/did/stats.py", line 135, in check
stat.check()
File "/usr/lib/python2.7/site-packages/did/stats.py", line 135, in check
stat.check()
File "/usr/lib/python2.7/site-packages/did/stats.py", line 80, in check
self.fetch()
File "/usr/lib/python2.7/site-packages/did/plugins/jira.py", line 137, in fetch
self.stats = Issue.search(query, stats=self)
File "/usr/lib/python2.7/site-packages/did/plugins/jira.py", line 94, in search
result = stats.parent.session.open(
File "/usr/lib/python2.7/site-packages/did/plugins/jira.py", line 265, in session
self._session.open(self.auth_url)
File "/usr/lib64/python2.7/urllib2.py", line 431, in open
response = self._open(req, data)
File "/usr/lib64/python2.7/urllib2.py", line 449, in _open
'_open', req)
File "/usr/lib64/python2.7/urllib2.py", line 409, in _call_chain
result = func(*args)
File "/usr/lib64/python2.7/urllib2.py", line 1242, in https_open
context=self._context)
File "/usr/lib64/python2.7/urllib2.py", line 1199, in do_open
raise URLError(err)
urllib2.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)>

Did I miss support for GitHub somewhere? It would be great to pull in stats about commenting, code reviews, etc...

As a bonus, and patches found with identical commit id's to something already mentioned in the git section, should probably be ignored.

Cheers!

Track activities for a given user in mojo.

Blog posts, document, pages, notes, created/modified.

Allowed arguments are described in usage string as
Usage: did [last] [week|month|quarter|year] [opts]

I would expect failure for each unrecognised positional argument. But that is only partially true:
$ did b
ERROR Invalid argument: 'b'

$ did a
Status report for this week (2015-09-21 to 2015-09-27).
...

AFAIK there should be no positional argument which 'a' matches.

Meetings attended are worth tracking... again, google should have an API that would enable users to get a list of meeting invites 'received', 'attended', 'rejected', 'maybed'

Right now the login/username is taken from the email (full email or username part, it seems). But different services could have different usernames. For example, my username here and then on review.gerrithub.io is ltoscano-rh, and this username is not part of any email. On the other side, my username on review.openstack.org (for example) matches my email.
So I think there should be a way to associate, for each user, some usernames specific to the various plugin instances.

Internally options.since and options.until dates are interpreted as the midnight of the respective date. This means that plugins need to query like this:

date >= options.since and date < options.since

This might be a little bit confusing at the first sight. But might be also useful as some services internally handle queries as datetime so for these you would have to say:

date > options.since and date < options.since

So the question is: Shall we leave it as it is? Or make the until option content match what is given on the command line? (Now --until 2015-10-03 is saved as 2015-10-04.)

According to Github API documentation, all results returning multiple items are paginated:
https://developer.github.com/v3/#pagination

While I didn't tested it yet, I think issue search is also paginated
(I tested get all issues for repo and that is paginated).

Lets use python requests, which provides nice functionality for handling pagination.
Will try to prepare PR, as I solved this already in my issue aggregator.

Statistics of closed bugs should be available too. Time spent by verification and closing of old/non-existing/non-resolvable bugs can be significant but valuable.

Some teams are filing status reports on another day than on the end of the week. It would be nice to be able to set in the configuration file a decisive day, so that user doesn’t have to apply --since every week.

[originally filed by Matěj Cepl]

I already have this partially done, but need to fix and extend some tests.

http://stackoverflow.com/questions/3217673/why-use-argparse-rather-than-optparse

Hi there,

any plan to extend did to connect to a google account and extract meetings from Google Calendar?

Using did from 80b4f9c and despite assurances on #43 DID_CONFIG variable doesn’t seem to make much difference:

matej@mitmanek: ~$ echo $DID_CONFIG
/home/matej/.config/did
matej@mitmanek: ~$ ls $DID_CONFIG/config
/home/matej/.config/did/config
matej@mitmanek: ~$ did --since=2015-09-22
Create at least a minimum config file /home/matej/.did/config:
[general]
email = Name Surname <[email protected]>
 ERROR  Unable to read the config file '/home/matej/.did/config'.
matej@mitmanek: ~$

There are lot of dotfiles in $HOME. But more and more projects moved to using ~/.config ~/.local etc directories instead of creating new ones.

Did should follow.

It is not always desirable to include all your GitHub contributions to your status report. Some of them might be commits/issues in your personal projects. Therefore, it would be nice to have some kind of filtering - either include list, exclude list or both options.

GitHub plugin currently does not show events such as comments or Pull Request review comments. Please add this so that selected event types can be shown along with issues.

Relevant doc: https://developer.github.com/v3/activity/events/

When path I specify as keeper of git repos [i.e. with /* expansion] contains non-repo directory, it fails with error complaining about GIT_DISCOVERY_ACROSS_FILESYSTEM not set.

 ERROR  fatal: Not a git repository (or any parent up to mount point /home)
 Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
 ERROR  Unable to check commits in '/home/dahaic/RH/git/tests/UPSTREAM'

If env variable is set, it fails nevertheless.

 ERROR  fatal: Not a git repository (or any of the parent directories): .git
 ERROR  Unable to check commits in '/home/dahaic/RH/git/tests/'

It would be nice to skip such directory and not fail.

All patches submitted for Gerrit review are listed not only in 'Changes submitted for review' section, but also in 'Additional patches added to existing changes'. This includes those Gerrit changes that contain a single patch set and have not been modified since their creation.

I can do did --since <yesterday's date>, but it would be sweet if this supported did yesterday.