Tim Harder
Tim Harder
Currently the man page mostly focuses on listing what functionality is available. It would probably be helpful to add a section on example workflow cases to leverage various functionality.
Now that pkgcheck has moved off readthedocs to gh-pages (https://pkgcore.github.io/pkgcheck), it should be easier to rework the look and feel to something more usable for casual browsers. This will probably...
As they're not up to date with regards to the massive restructuring that occurred to make parallelism viable. It could be nice adding a few examples for writing custom checks...
This wouldn't get run by default, but would be useful as a metric to know when test run times for static data regress or improve significantly especially as work is...
This could either mean ebuilds sitting in a dir somewhere outside a repo or an ebuild piped into stdin. Most relevant checks would have to be reworked a bit to...
The docs currently consistent of an entirely generated man page.
Currently `pkgdev commit` and `pkgdev push` use the GentooCI checkset defined internally by pkgcheck, but it could be nice to allow discerning users to alter the keyword set that triggers...
Without proper bash parsing support, this could still do things like updating file headers and fixing EOF lines and the functionality should be available for external use so `pkgdev commit`...
Probably makes sense to limit it to package scope on the initial implementation. As a rough overview, the workflow would be similar to this: 1. Lots of ebuild changes are...
So users can change what wording commit message templates use to their own personal preference more easily than changing the code itself.