Re: git: 7f8b4db9e001 - main - github: Add more context to pull requests

On Tue, Jan 13, 2026 at 7:56 AM John Baldwin <jhb@freebsd.org> wrote:

> On 1/12/26 02:37, Warner Losh wrote:
> > The branch main has been updated by imp:
> >
> > URL:
> https://cgit.FreeBSD.org/src/commit/?id=7f8b4db9e001d94974a081e5fd58c4f3994429cb
> >
> > commit 7f8b4db9e001d94974a081e5fd58c4f3994429cb
> > Author:     Warner Losh <imp@FreeBSD.org>
> > AuthorDate: 2026-01-10 16:20:20 +0000
> > Commit:     Warner Losh <imp@FreeBSD.org>
> > CommitDate: 2026-01-12 07:18:11 +0000
> >
> >      github: Add more context to pull requests
> >
> >      Add code to fetch and decode CODEOWNERS and automatically @ people
> in
> >      the review.
> >
> >      Create a new file, .github/path-rules.txt that has a set of paths to
> >      match and specific warnings about that part of the tree. We'll use
> this
> >      to try to wave off pull requests in certain areas of the tree, as
> well
> >      as remind people when contrib is involved, etc.
> >
> >      Sponsored by:           Netflix
> > ---
> >   .github/path-rules.txt          |  10 ++++
> >   .github/workflows/checklist.yml | 106
> ++++++++++++++++++++++++++++++++++++----
> >   2 files changed, 106 insertions(+), 10 deletions(-)
> >
> > diff --git a/.github/path-rules.txt b/.github/path-rules.txt
> > new file mode 100644
> > index 000000000000..297cfe8def35
> > --- /dev/null
> > +++ b/.github/path-rules.txt
> > @@ -0,0 +1,10 @@
> > +#
> > +# Format the similar to CODEOWNERS: Each line has a path, whitespace
> and a
> > +# message for contributors.
> > +#
> > +sys/contrib/device-tree      :caution: No changes should be made here
> by pull request
> > +# Catch all
> > +contrib              :warning: Contributed software usually managed by
> vendor branch
> > +crypto               :warning: Contributed crypto software usually
> managed by vendor branch
> > +sys/contrib  :warning: Contributed software usually managed by vendor
> branch
> > +sys/crypto   :warning: Contributed crypto software usually managed by
> vendor branch
>
> sys/crypto isn't really the same.  We store the generated OpenSSL assembly
> files there
> for use by ossl(4), but most of sys/crypto is not vendored (e.g. ccp, the
> non-assembly ossl
> bits, aesni are all just bespoke).
>

That's the beauty of this: We can have whatever we want here...  These were
placeholders until
we had more nuanced things. I see things like openssh in crypto too, so
many things are
vendored there, in addition to the mire of inconsistency... First one wins
(or did I take that out,
if I did, I should put it back)....  I'd also thought this might couple
well with the 3rd party audit
and we could generate some json from that to give upstream pointers,
project contacts, etc
around all that.

But maybe just

:caution: Cryptographic software requires special care that the project
cannot give to pull requests.

Warner