Skip to main content

Contributing

还没翻译译自英文（docs.langchain.com）本页 35 段都还没译

Welcome! Thank you for your interest in contributing.

LangChain has helped form the largest developer community in generative AI, and we're always open to new contributors. Whether you're fixing bugs, adding features, improving documentation, or sharing feedback, your involvement helps make LangChain and LangGraph better for everyone 🦜❤️

Ways to contribute

Issues and pull request requirements

You can submit pull requests for typos and small fixes directly, without an issue, prior maintainer approval, or assignment.

Warning

Larger changes, such as new tutorials, guides, or conceptual pages require a linked issue and maintainer approval before you open a pull request. Wait until a maintainer has approved your approach and assigned the issue to you. Larger PRs opened before approval and assignment may be closed automatically and are not reviewed until assignment.

All pull requests should demonstrate meaningful effort and contextual understanding. If the effort required to create a pull request is less than the effort required for maintainers to review it, that contribution should not be submitted. Low-effort drive-by contributions—regardless of how they are produced—often miss the mark in terms of contextual relevance, accuracy, and quality. Mass automated contributions represent a denial-of-service attack on our human effort.

Warning

We prioritize issues motivated by actual usage. Issue boards are a mechanism for allocating maintainer attention. They are not a comprehensive catalog of every statically-discoverable defect. Please avoid submitting issues discovered by (AI) code-scanning without first personally validating them and grounding them in real usage of LangChain's public APIs. If maintainers suspect an issue has not been validated it may be closed without review, and the authoring account may be blocked.

The following requirements must be met for all external pull requests:

  • For larger changes, link to an issue where a maintainer has approved your approach and assigned it to you before opening the PR. Typos and small fixes are exempt from this requirement.
  • The pull request must fill in the repository's pull request template.
  • Pull requests for net new features or behavior-changing bugfixes should include a ## Release note section that states the user-visible change in release-note-ready language.

Maintainers reserve the right to close PRs without comment if these requirements are not met. We will close pull requests and issues that appear to be low-effort spam.

Language policy

All contributions—issues, pull requests, code reviews, and discussions—must be in English. This keeps communications accessible and searchable across our global contributor base.

If English isn't your first language, don't worry. We value clear communication over perfect grammar, and translation tools are welcome.

Acceptable uses of LLMs

You may use AI assistants to help draft or revise contributions when you verify every change: run and test code, check facts against the codebase and official provider docs, and ensure the result matches repository style. Do not submit bulk, unreviewed generated content. We close pull requests that read as low-effort or spam regardless of how they were produced.

AI 翻译查看英文原文