While this particular change does not qualify because the only code change is to the plugin file (and I only make changes to that file in master), make all future code contributions against the dev branch instead of master. If you checkout my dev branch locally before you make the changes and commit them it will automatically try to open the PR against my dev branch next time.
My personal policy is I won't accept binary data in a pull request unless it is a type of media (image data). By you running the package creation script and committing the result, I am bound to not only review the changes you made in my codebase but also to check the contents of the .txz file that was created. @mlapaglia did the same with his previous PR and I had him revert his branch as well.
After reviewing your commits, I only need the first one. Go back into your local branch, and issue:
Okay, so two things:
After reviewing your commits, I only need the first one. Go back into your local branch, and issue:
It should auto update this PR to only include your original gpustat.plg changes. From there, I will run the script to author the package.