Re: [edk2-devel] EDK II Maintainers - EDK II CI is now active on edk2/master

["Laszlo Ersek" <lersek@redhat.com>]

Hi Mike,

On 11/12/19 03:55, Michael D Kinney wrote:
> EDK II Maintainers,
> 
> EDK II CI Phase 1 feature is now active on edk2/master.
> 
> Please use a GitHub pull request from a branch in a personal
> fork of the edk2 repository with a 'push' label to request
> a set of patches to be pushed to edk2/master.  The GitHub PR
> replaces the 'git push' operation currently used to commit
> changes to edk2/master.
> 
> You will need to configure your notifications from the edk2
> repository to make sure you receive email notifications
> when the checks against the GitHub PR passes or fails.
> 
> If you submit a GitHub Pull Request without the 'push'
> label, then the CI checks are run and the results are
> generated.
> 
> Please let us know if there are any questions about this
> change in the development process.

I had filed

  https://bugzilla.tianocore.org/show_bug.cgi?id=2406

a month ago, about PatchCheck.py being too strict, and blocking pull requests unjustifiedly.

Now I realize I can't even review the results (= the PatchCheck.py error messages) on github.com and/or on Azure Pipelines:

  https://github.com/tianocore/edk2/pull/272/checks?check_run_id=375969977
  https://dev.azure.com/tianocore/11ea4a10-ac9f-4e5f-8b13-7def1f19d478/_build/results?buildId=3456

Am I looking in the wrong place perhaps?

Can we please add a manual PatchCheck.py override on github.com for those maintainers that are permitted to set the "push" label already?

TianoCore#2406 doesn't seem to be getting any attention, and it is blocking actual development work.

Thanks
Laszlo