search

psss / did

What did you do last week, month, year?
https://did.readthedocs.io/
GNU General Public License v2.0
246 stars 104 forks source link

Filter git reporting by type? #306

Open daobrien opened 1 year ago

daobrien commented 1 year ago

Is it possible to filter the output of git reporting to see, or not see, different types or classes?

E.g., I want to see all the issues and PRs that I opened, reviewed, or closed, but not all the issues that I commented on.

I haven't been able to find any docs on how to set up filters in the config file. Thanks

psss commented 1 year ago

As for now this is only possible through command line options, for example like this:

> did --github-issues-created --github-pull-requests-created last month
Status report for května (2023-05-01 to 2023-05-31).

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Petr Šplíchal <psplicha@redhat.com>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

* Issues created on github: 2
    * teemtee/tmt#2063 - Repeated failures when fetching the `centos:7` image
    * teemtee/tmt#2054 - Use consistent format for all multiword keys

* Pull requests created on github: 3
    * beakerlib/libraries#011 - Update the list of existing libraries
    * teemtee/fmf#191 - Update pre-commit checks to the latest versions
    * teemtee/tmt#2055 - Request newer os image and python version for docs

Having the same possibility in the config file could be useful.

daobrien commented 1 year ago

Would def be useful in the config file because I have GH, Jira, and Trello all set up. Thanks. (I'm not a coder so not really something I could tackle.)

psss commented 1 year ago

Sorry, currently I don't have capacity for implementing this but it's definitely open for anyone interested to submit a patch.

daobrien commented 1 year ago

Sorry, currently I don't have capacity for implementing this but it's definitely open for anyone interested to submit a patch.

No worries. I'm trying to find time to have a go at #305 and I'll try to get one of my coder friends interested in this one. Thank you again for did.

psss commented 1 year ago

No worries. I'm trying to find time to have a go at #305 and I'll try to get one of my coder friends interested in this one.

Nice!

Thank you again for did.

Thanks for the feedback :)