github Issues and PR

[Petr Lautrbach <lautrbach@redhat.com>]

Pepper Gray <hello@peppergray.xyz> writes:

> Hi Petr,
>
...

> I will investigate how to send patches in the proper format. Please note
> that your Github is quite frustrating and consider disabling Issues and PRs
> there if nobody is gonna look at them anyways!

If a PR is opened via web page, there's this template:

    Please read [CONTRIBUTING.md](https://github.com/SELinuxProject/selinux/blob/main/CONTRIBUTING.md)
    
    
    ## Contributing Code
    
    Post the patch for the review to the
    [SELinux mailing list](https://lore.kernel.org/selinux) at
    [selinux@vger.kernel.org](mailto:selinux@vger.kernel.org).
    
    When preparing patches, please follow these guidelines:
    
    -   Patches should apply with git am
    -   Must apply against HEAD of the main branch
    -   Separate large patches into logical patches
    -   Patch descriptions must end with your "Signed-off-by" line. This means your
        code meets the Developer's certificate of origin, see below.


I guess that it's not shown when a PR is opened via some tool. Sometimes PRs
are used by the team to trigger CI or when it's not possible to send a
patch due to the size limitation on the mailing list

As for Issues, they are monitored even though not consistently.

It's clearly stated in the
https://github.com/SELinuxProject/selinux/blob/main/CONTRIBUTING.md that
bugs and patches should be sent to the mailing list.

Leaving both open should make the contribution for people using github
more accessible even trhough we don't really use it.


Petr