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
We still have some 20 issues to deal with, and in the meantime are thinking about the implications of going public when most of the issues are closed. Would there be any interest to incorporate our work in the gitinspector repo? I would be willing to dedicate project resources to the fixing of reported bugs.
The main characteristics of the project follow below.
Addition of a GUI, based on PySimpleGUI, see example picture below.
Generation of standalone gitinspector executables, via pyinstaller, for CLI and GUI, for Windows and Mac.
New output formats CSV and Excel with new multi-repo functionality, that shows the output separately for each of the analysed repos in a single output file. See picture below for three repos: a12e12, jplag and gitinspector.
Option to deal with authors using multiple email addresses in a repo, and vice versa.
Multiple test sets, and all code formatted using the automatic Black formatter.
Use of the following packages with Python 3.10.8:
Replacement of all git and subprocess calls by GitPython commands, leading to shorter code that is easier to use and change. This is still work in progress.
Use of pathlib for all file IO.
Use of argparse for generation of all options, both for the CLI and GUI.
In principle, the GUI and CLI are backwards compatible to the current gitinspector functionality.
The text was updated successfully, but these errors were encountered:
Yes I most definetly think this could be something :) ... Exactly how to go about it though and keep everything in sync.... That's a different question :) ....
Maybe it's time for a gitinspector group/team so we can collect efforts like these under the same organisation.
As part of a bigger project (https://boost.tue.nl/projects/ict-tools-to-support-tpil-in-project-groups/), we have been working for a few years on a GUI and apps for gitinspector. The apps have been developed, tested and used via a private GitLab repository, forked from gitinspector.
We still have some 20 issues to deal with, and in the meantime are thinking about the implications of going public when most of the issues are closed. Would there be any interest to incorporate our work in the gitinspector repo? I would be willing to dedicate project resources to the fixing of reported bugs.
The main characteristics of the project follow below.
The text was updated successfully, but these errors were encountered: