docs: added a link to the taxonomy of labels in the contributing guide for easy access

[bjoaquinc]

Thank you for contributing to LangChain!

• PR title: "package: description"

  • Where "package" is whichever of langchain, community, core, etc. is being modified. Use "docs: ..." for purely docs changes, "infra: ..." for CI changes.
  • Example: "community: add foobar LLM"

• PR message: Delete this entire checklist and replace with

  • Description: Added a link to make it easier to organize github issues for langchain.
  • Issue: After reading that there was a taxonomy of labels I had to figure out how to find it.
  • Dependencies: None
  • Twitter handle: None

• Add tests and docs: If you're adding a new integration, please include

  1. a test for the integration, preferably unit tests that do not rely on network access,
  2. an example notebook showing its use. It lives in docs/docs/integrations directory.

• Lint and test: Run make format, make lint and make test from the root of the package(s) you've modified. See contribution guidelines for more: https://python.langchain.com/docs/contributing/

Additional guidelines:

• Make sure optional dependencies are imported within a function.
• Please do not add dependencies to pyproject.toml files (even optional ones) unless they are required for unit tests.
• Most PRs should not touch more than one package.
• Changes should be backwards compatible.
• If you are adding something to community, do not re-import it in langchain.

If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, ccurme, vbarda, hwchase17.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
langchain	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 14, 2024 2:33am

[efriis]

chatting with the team on what is most useful here. I think listing a few specific ones is probably more useful than the exhaustive list!

[bjoaquinc]

chatting with the team on what is most useful here. I think listing a few specific ones is probably more useful than the exhaustive list!

Yeah I think this is a great idea! Navigating issues has been very confusing and It would make understanding and filtering issues a lot easier for prospective contributors like myself.

Want me to create an label-taxonomy.mdx file here after you and the team decide on which specific tags to highlight?