mirror of
https://github.com/hwchase17/langchain.git
synced 2026-03-18 02:53:16 +00:00
cb50fed2bb
Bypass the issue-link requirement for external contributors who have earned the `trusted-contributor` tier label (>=5 merged PRs). Previously only PRs with the `internal` label skipped the gate, meaning repeat contributors still had to link an approved issue on every PR. Also includes minor template and linting tweaks for contributor experience. ## Changes - Add `trusted-contributor` bypass to the `check-issue-link` job condition in `require_issue_link.yml`, with a secondary live-label API fetch inside the script to cover the race where the `external` labeled event payload doesn't yet include the tier label - Add a `bypass-trusted-contributor` job in `require_issue_link.yml` that removes `missing-issue-link` and reopens the PR when the `trusted-contributor` label arrives after enforcement has already closed it - Reorder steps in `tag-external-contributions.yml` so the tier label is applied *before* the `external` label — eliminates the race window entirely since `trusted-contributor` is already on the PR when the downstream `labeled` event fires - Switch the tier-label step from `GITHUB_TOKEN` to the app token so the `trusted-contributor` labeled event propagates to downstream workflows - Add `hotfix` to allowed PR title types in `pr_lint.yml` - Promote the English language policy to a blockquote callout in issue and PR templates; add a "do not begin work without assignment" note to the feature request template
44 lines
2.2 KiB
Markdown
44 lines
2.2 KiB
Markdown
Fixes #
|
|
|
|
<!-- Replace everything above this line with a 1-2 sentence description of your change. Keep the "Fixes #xx" keyword and update the issue number. -->
|
|
|
|
Read the full contributing guidelines: https://docs.langchain.com/oss/python/contributing/overview
|
|
|
|
> **All contributions must be in English.** See the [language policy](https://docs.langchain.com/oss/python/contributing/overview#language-policy).
|
|
|
|
If you paste a large clearly AI generated description here your PR may be IGNORED or CLOSED!
|
|
|
|
Thank you for contributing to LangChain! Follow these steps to have your pull request considered as ready for review.
|
|
|
|
1. PR title: Should follow the format: TYPE(SCOPE): DESCRIPTION
|
|
|
|
- Examples:
|
|
- fix(anthropic): resolve flag parsing error
|
|
- feat(core): add multi-tenant support
|
|
- test(openai): update API usage tests
|
|
- Allowed TYPE and SCOPE values: https://github.com/langchain-ai/langchain/blob/master/.github/workflows/pr_lint.yml#L15-L33
|
|
|
|
2. PR description:
|
|
|
|
- Write 1-2 sentences summarizing the change.
|
|
- The `Fixes #xx` line at the top is **required** for external contributions — update the issue number and keep the keyword. This links your PR to the approved issue and auto-closes it on merge.
|
|
- If there are any breaking changes, please clearly describe them.
|
|
- If this PR depends on another PR being merged first, please include "Depends on #PR_NUMBER" in the description.
|
|
|
|
3. Run `make format`, `make lint` and `make test` from the root of the package(s) you've modified.
|
|
|
|
- We will not consider a PR unless these three are passing in CI.
|
|
|
|
4. How did you verify your code works?
|
|
|
|
Additional guidelines:
|
|
|
|
- All external PRs must link to an issue or discussion where a solution has been approved by a maintainer, and you must be assigned to that issue. PRs without prior approval will be closed.
|
|
- PRs should not touch more than one package unless absolutely necessary.
|
|
- Do not update the `uv.lock` files or add dependencies to `pyproject.toml` files (even optional ones) unless you have explicit permission to do so by a maintainer.
|
|
|
|
## Social handles (optional)
|
|
<!-- If you'd like a shoutout on release, add your socials below -->
|
|
Twitter: @
|
|
LinkedIn: https://linkedin.com/in/
|