Making it easier to contribute to LangChain

[Mason Daugherty (mdrxy)]

We shipped a few changes to how external contributions work. The goal is to save contributors time by aligning on scope before code gets written, and to help maintainers prioritize reviews more effectively.

Talk to us before you code

External PRs now need to reference an approved issue (Fixes #123, Closes #123, or Resolves #123 in the PR description), and you need to be assigned to that issue. PRs that don't meet these requirements will be automatically closed — but don't worry, the bot will tell you exactly what's missing, and your PR will reopen automatically once everything checks out.

The quick version:

1. Find an existing issue or open a new one
2. Comment with a brief plan for how you'd approach the fix or feature (a few sentences is plenty)
3. Once a maintainer approves and assigns you, open your PR with Fixes #<number> in the description before any other content

We especially encourage issue authors to contribute fixes — you're closest to the problem and most likely to understand the context. This process keeps everyone on the same page and avoids the frustration of putting work into a PR that we can't merge.

For the full rundown on contributing, check out our Contributing Guide.

We now recognize repeat contributors

If you've had 5 or more PRs merged, you'll automatically get a trusted-contributor label on your PRs and issues. This helps maintainers spot familiar faces during triage. If you've been contributing for a while — thank you, and your PRs will reflect that now.

FAQ

I'm assigned to an issue but the check still failed?
Make sure your PR description includes one of the auto-close keywords (Fixes, Closes, or Resolves) followed by the issue number. The check re-runs when you edit the description.

---

This is a new process and we're iterating on it. If something feels off or you have suggestions, let us know in this thread.

[Baixin Guo (GBX-Max1220)]

No comments ？

[Mason Daugherty (mdrxy)]

hi Baixin Guo (@GBX-Max1220) can you elaborate?

[ANIRUDDHA ADAK (aniruddhaadak80)]

From my point of view, this is a sensible change because it prevents contributors from doing a lot of work on PRs that were never aligned with maintainer priorities.

The only friction I would watch is the gap between opening an issue and knowing whether it is actually ready for outside work. A lightweight label or maintainer note like ready for external contribution would probably reduce the back and forth a lot for new contributors.

The trusted contributor signal also seems useful. It gives repeat contributors a clearer path without weakening the review process for brand new proposals.

[Mason Daugherty (mdrxy)]

Hi ANIRUDDHA ADAK (@aniruddhaadak80) thank you for the feedback!

knowing whether it is actually ready for outside work

We will tag issues with the help wanted label for things we'd invite people to request be assigned on -- see the contributing guide for more.

[Son Seong Jun (SonAIengine)]

Makes sense for feature work, but curious how this plays out for docs fixes or small tweaks — doesn't want the overhead to kill those contributions. Probably already thought through it, but worth calling out since those PRs add up.

[Assad Yousuf (assadyousuf)]

Mason Daugherty (@mdrxy) You should really consider a way of banning potential contributors that just endlessly open up PRs and issues. It's clear people are setting their agents to essentially DDOS maintaners with slop. Super fustrating the good trusting nature of open source is dying.

[Mason Daugherty (mdrxy)]

We are able to ban users from contributing/commenting/opening PRs/etc. and have done so. That process is currently manual.