Inquisitor hasn't seen very much love in a while.
The main thing is that it should be scoped, as the lack of scoping (or indeed any way of reducing the amount of work it does) significantly limits its usability. Currently, inquisitor runs on the entire repository regardless of your working directory.
Instead, it should only run on the current directory, and subdirectories of the current directory. I.e. running it from a package directory will run it on the package, from a category will run it on all packages on the category, and running it from the root will run it on everything in the repository.
Features such as those employed by pkgcheck would also be useful. See https://blogs.gentoo.org/mgorny/2019/12/12/a-better-ebuild-workflow-with-pure-git-and-pkgcheck/
In short, this would be:
- A way of getting it to validate packages changed by "new" commits (compared to the origin? (not really sure that's useful, as I generally use origin for my fork, and upstream for openmw-mods, but others may do differently), compared to the most recent branch point?).
- Checking commit messages in those recent commits to ensure that they are formatted to include the qualified package name in the header line.
commitsubcommand which can generate commit messages based on staged changes (e.g.
CMN: Added $MV, if a new version of a package was added, or
CMN: Bumped to $MVif renamed to a new version)