Currently patchtest takes any new series event, no matter what the submitter is, and post results to patchwork. This is the general usage but for the moment, it would be useful to just take into consideration selected people (patchtest or patchtest-oe developers), so in the testing phase, the patchwork/test do not spam others with mails that may not be relevant at this moment.
This is something to be implemented before production.
The feature is implemented using a command line argument, which is a string indicating a python regular expression. This regex is scanned into the item's submitter, if match then the POST request is done. By default, this regex is empty, so no post is done. Command line example: # No posting git pw poll-events | patchtest # post all series, not matter the submitter git pw poll-events | patchtest --include-post-users '.*' # post series for those submitters with email's host/domain 'linux.intel.com' git pw poll-events | patchtest --include-post-users '.*@linux.intel.com'
(In reply to comment #2) > The feature is implemented using a command line argument, which is a string > indicating a python regular expression. This regex is scanned into the > item's submitter, if match then the POST request is done. By default, this > regex is empty, so no post is done. > > Command line example: > > # No posting > git pw poll-events | patchtest > > # post all series, not matter the submitter > git pw poll-events | patchtest --include-post-users '.*' > > # post series for those submitters with email's host/domain 'linux.intel.com' > git pw poll-events | patchtest --include-post-users '.*@linux.intel.com' Small change done, now the parameter a simpler name: '--post-submitters' or simple '-p'