You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For instance, the following command took 6 seconds on my machine:
$ time hubstats -o vidal-community -r atom-jaxb
pull requests for vidal-community/atom-jaxb ->
since 2019-12-26T18:04:13Z
0 opened / 0 closed / 0 commented (0 comments)
opened per author: {}
comments per author: {}
closed per author: {}
hubstats -o vidal-community -r atom-jaxb 4.90s user 0.32s system 86% cpu 6.052 total
Using pullpitoK, the equivalent command takes 1 second on my machine:
$ time pullpitoK vidal-community/atom-jaxb
pull requests for"vidal-community/atom-jaxb" ->
opened per author
amairi: 1
commented per author
AElMehdiVidal: 1
jcgay: 1
closed per author
Note that the output is different because hubstats retrieves changes for last 7 days (--since-weeks has a default value of 1). 😇
The text was updated successfully, but these errors were encountered:
Investigate if latency can be enhanced.
For instance, the following command took 6 seconds on my machine:
Using pullpitoK, the equivalent command takes 1 second on my machine:
Note that the output is different because
hubstats
retrieves changes for last 7 days (--since-weeks
has a default value of 1). 😇The text was updated successfully, but these errors were encountered: