The Godot engine team, renowned for powering indie roguelikes such as Brotato and the forthcoming sequel to Slay the Spire, has taken a decisive stance: AI‑generated pull requests are no longer welcome. The sheer volume of machine‑made submissions has overwhelmed human reviewers, prompting this hardline policy.
As AI tools grow more sophisticated, the effort required to submit a pull request has dropped dramatically, yet the time maintainers spend scrutinizing these contributions has surged—while the pool of reviewers remains unchanged.
Reviewing AI‑generated code has become disheartening for volunteers. In the past, contributors poured hours into crafting code, and reviewers felt their guidance helped nurture new developers. Now, reviewers sense their feedback is ignored because large language models cannot learn from specific critique.
Volunteer maintainers are reluctant to expend their limited free time dissecting code that will never be corrected or promoted to a maintainer, especially when the bot cannot improve from the review.
Going forward, any pull request composed entirely of AI‑generated code will be rejected. Developers may still employ AI for minor tasks—such as regex, translations, code completion, or simple find‑and‑replace—provided they transparently disclose this assistance in the pull request discussion.
The influx of low‑effort, AI‑generated pull requests is putting unprecedented pressure on open‑source projects. Just last month, the fledgling Ladybird Browser—an entirely original browser engine built from scratch—halted all external contributions, closing every pending pull request after realizing that vetting unverified AI code posed unacceptable security risks.
Earlier this year, cURL, the widely used command‑line utility, discontinued its bug‑bounty scheme after a wave of malicious actors leveraged AI agents to flood the program with fabricated vulnerability claims and contrived patches for phantom bugs, all in pursuit of quick financial gain.
❓ Frequently Asked Questions (FAQ)
Why has the Godot engine team decided to ban AI-generated pull requests?
The team found that the sheer volume of machine‑made submissions overwhelmed human reviewers, leading to a surge in review time while the reviewer pool remained unchanged. Reviewing AI‑generated code became disheartening for volunteers, as the feedback they provide is often ignored by large language models that cannot learn from specific critique. This imbalance prompted the hardline policy to protect maintainers’ limited free time and maintain code quality.
Can developers still use AI tools when contributing to Godot?
Yes. Developers may employ AI for minor tasks such as generating regex, translating text, completing code snippets, or performing simple find‑and‑replace. However, they must transparently disclose any AI assistance in the pull request discussion. Pull requests composed entirely of AI‑generated code will be rejected.
What does this policy mean for the sustainability of open‑source communities?
It highlights the tension between rapid AI‑driven code generation and the capacity of volunteer maintainers. By limiting AI‑only contributions, the policy aims to preserve reviewer engagement, ensure meaningful mentorship, and prevent the dilution of code quality, thereby supporting the long‑term health of open‑source projects.
News Source: Neowin
Comments
Be the first to comment.