How GitHub PR limits help maintainers stop AI slop
Read the Portuguese translation →
Author: GitHub · Watch on YouTube
Video authored by the channel shown, not by IANIA; all rights belong to the creator. Transcript and summary generated automatically; the original-language content is preserved.
Original language: English
Original video: How GitHub PR limits help maintainers stop AI slop · Channel: GitHub · 01:02 · Watch on YouTube
Topics: Software engineering with AI, Open source and software ecosystems
Summary
Section titled “Summary”GitHub describes PR limits as a tool to help maintainers manage the increase in low-quality contributions, referred to in the transcript as the “AI slot problem.” The feature lets maintainers limit how many pull requests users without write access can have open at once. The team is exploring more granular controls, including counting draft PRs toward the limit and automatically bypassing limits for users who have established trust in a repository.
Key points
Section titled “Key points”- Low-quality contributions have become a major pain point for repositories.
- GitHub says it is working on tools to support maintainers handling contributions at scale.
- PR limits let maintainers cap the number of open PRs from users without write access.
- The team is considering an option to count draft PRs toward the limit.
- A maintainer says unwanted draft PRs can remain in a project’s history.
- GitHub is also exploring automatic limit bypasses for users trusted by a repository.
- The proposed trust-based bypasses would use different criteria.
Chapters
Section titled “Chapters”| Start | Chapter | Summary |
|---|---|---|
| 00:00 | PR limits for maintainers | GitHub explains that PR limits were introduced to help maintainers respond to rising numbers of low-quality contributions. |
| 00:31 | More granular controls | The speakers discuss counting draft PRs toward limits and the problem of unwanted drafts lingering in project history. |
Quotes
Section titled “Quotes”we shipped PR limits — 00:00
adding a setting to allow draft PRs to count towards that limit — 00:31
I don’t want this random PR sitting in my history — 00:31
adding more ways to automatically bypass users from these limits if they’ve established trust in a repo — 01:02
Concepts and entities
Section titled “Concepts and entities”AI slop, PR limits, draft PR, GitHub, open source
Full transcript (original language)
Section titled “Full transcript (original language)”00:00 When the number one pain point became the increase in low quality contributions hitting repos, which we’ve been calling the AI slot problem. So since then, we’ve kind of had all hands on deck to try to help solve this problem and figure out more ways and more tools to help support open source maintainers dealing with contributions hitting their repos at scale. So most recently, we shipped PR limits, which basically allows maintainers to set a maximum number of PRs
00:31 that users without write access can have open at once. And what we’re doing now is handy on top of that. >> Yeah, so finding more ways to make it more granular. >> Um so for example, one thing that we’re working on is adding a setting to allow draft PRs to count towards that limit so that you don’t all of a sudden become spammed. >> Yes. I want that. >> Have you Yeah, have you had that happen to you? >> Just on a couple of my projects where I’m just like, “Could you get rid of that? I don’t It’s It’s It’s just there where I don’t want this random PR
01:02 sitting in my history, but it is.” >> Yeah, yeah. Um okay, well hopefully we’ll have that out soon. Uh and then just like adding more more ways to automatically bypass users from these limits if they’ve established trust in a repo kind of based on different criteria. >> Oh, that sounds so useful. That’s something I will definitely use. I’m so excited that your team is working on that.