Hi Miro,
that's a really valid point that we should somehow resolve. Is this always the case with the mass rebuilds that they should be left unbuilt or just with your Python rebuilds?
I am thinking about multiple options here:
1) configurable allow-list / block list for committers (for the user and/or for the whole service)
* For our projects, we would allow just the `packit` user that we use for submitting the dist-git pull requests.
* We could probably react to just `packit` commits for all the users but I don't like this all-or-nothing approach. (That people are required to use all the Packit's features or none.)
2) check the committer for not being a proven packager (Packit is not a proven packager and we don't want to change that. We would like to have as few permissions as possible.)
* I don't see any technical problem with the implementation here and personally see this as a possible solution.
3) use a commit message to skip/trigger the build
* We can't inform everyone about this feature so skipping the build by commit command is probably not a good idea.
* And forcing the commit structure to trigger the build makes it hard to use.
We can probably think about this more, but the second option looks the best for me so far. Automation is not reduced and work for proven packagers is untouched. What do you think? Would this work for you? Or, do you have any better idea/solution?
Thanks for bringing this up!
František