PR Owner might be something that could be exposed, but it definitely isn't tracked right now. This might require changes in scm-api-plugin or branch-api-plugin as well.

It would actually be a very interesting enhancement.
I would even say that I am really surprised that we cannot send a mail to the user having created a PR that on its turn trigger a build !

Is this different from the information that GitHub Branch Source already provides in a ContributorMetadataAction (javadoc)? That was added in https://github.com/jenkinsci/github-branch-source-plugin/pull/113 before github-branch-source-2.0.1.

https://github.com/jenkinsci/email-ext-plugin/search?q=ContributorMetadataAction doesn't find any references to ContributorMetadataAction in email-ext-plugin. Perhaps this issue should be moved to the email-ext-plugin component as a request to add a RecipientProvider that checks for ContributorMetadataAction. According to https://www.jenkins.io/doc/developer/extensions/email-ext/#recipientprovider, no other plugins implement RecipientProvider yet.

Oh, there is JENKINS-62079 for email-ext-plugin already.

I'm resolving this as fixed because the plugin apparently adds ContributorMetadataAction, which matches the description of this feature. Please reopen if you disagree.

Released As        GitHub Branch Source 2.0.1
Resolution        Fixed [ 1 ]
Status    Open [ 1 ]    Resolved [ 5 ]

I am confused. GitHub Branch Source release 2.0.1 is a 5 year old release.

I am guessing it's because it was fixed in email-ext in JENKINS-62079 and perhaps you cannot close a ticket without putting a value in the Released As field?  Maybe resolving as a duplicate or something might have been more clear.

In any case, I will try the updated email-ext plugin.

Thanks!

AFAICT, this feature was implemented in https://github.com/jenkinsci/github-branch-source-plugin/pull/113, which was merged in January 2017. I don't know why bitwiseman wrote that this "definitely isn't tracked".