Repository member role labels now in the pull request list view

[moraesc]

We're excited to announce that contributor role labels are now available directly in the pull request list view for public repositories.

Check out the changelog for more details.

Why are we releasing this?

Maintainers are consistently seeing an increase in pull request volume and particularly in low-quality contributions. For teams managing active repositories, this creates a real challenge: determining which pull requests warrant immediate attention, which require additional guidance, and where limited review time is best spent.
 
Contributor context plays a critical role in making those decisions effectively. Previously, repository role labels were only visible within the pull request comment box, requiring maintainers to open each pull request individually to assess contributor context. For teams managing high volumes of contributions, this added unnecessary friction to an already demanding workflow.
 
This release brings repository role labels directly into the pull request list view, giving maintainers the context they need to make faster, more informed decisions while triaging PRs and determining what should be prioritized.

How does this help you?

• Triage pull requests faster - understand a contributor's history at a glance, without opening each PR individually.
• Surface first-time contributions - spot new contributors right from the list view so you can give them the attention and welcome they deserve.
• Better prioritize your review queue - focus your energy where it matters most by being able to triage more efficiently.

We want your feedback!

We'd love to know how these labels are helping you. A few things we're curious about:

• Has this helped you triage or prioritize pull requests more effectively?
• Are there other places in the GitHub UI where you'd like to see contributor role labels?
• Is there other information you’d like to see in the PR list view?

If you have any questions or feedback, drop a comment below!

[Takhoffman]

This is great thank you. It'd be nice if we could somehow surface number of merged PRs by a contributor or be able to more easily identify a "trusted contributor".

I'd also like to be able to add hidden labels. These are labels that would only be visible to maintainers/Apps. The reason for this is to be able to label PRs for automation purposes and keep them hidden from the general public in such cases they are identifying low value PRs or spam. Keeping them hidden will help avoid drama and hurt feelings while still enabling automation.

[moraesc]

@Takhoffman we're looking into all of this! We're hoping to surface more information to help maintainers triage so will keep this in mind. Hidden labels makes sense too - ideally only maintainers see more sensitive information.