mirkoledda / git-summary Goto Github PK

I have a directory with 154 repos in it.
git-summery only outputs around 55 of those repos (random set)
This is without arguments.
With arguments (like -q) it is hit or miss if it actually finds the repos that have differences.

Here for example I did two runs immediately after each other.
one run it finds the two repos that are out of sync, and in another it does not find them.

> git-summary -q

Repository                              Branch  State
======================================  ======  =====
Checked 154 repositories.
>

> git-summary -q

Repository                              Branch  State
======================================  ======  =====
./fsyslog                               master     v 
./vault                                 master     v 
Checked 154 repositories.
>

With -s (sort) all the repos does seem to be found successfully.
So it is likely something to do with the race condition you mentioned as part of this option.

Hey,

Debian no longer provides an executable named python by default[1][2], so relative repo paths don't work out of the box. Is this something you'd want to handle? Some options could be:

• If you want to keep the code as is, then Debian users can install the python-is-python3 package to create the python -> python3 symlink, but this is a manual step that they have to know about.
• The code could check for the existence of either python3 or python2 executables (...or just python3 if py2 compatibility isn't a concern).
• I see there is a realpath --relative-to= option, I'm not sure if it this is equivalent to Python's os.path.relpath() but maybe the dependency on Python isn't needed.

[1] https://wiki.debian.org/Python
[2] https://www.debian.org/doc/packaging-manuals/python-policy/#unversioned-python-commands

It would be a lot better if the git-summery did NOT list the full path to the repository, but one relative to the current directory, or the directory given as an argument
Much like 'ls' and 'find' would.