langchain-ai/docs
1
0
Fork 0
mirror of https://github.com/langchain-ai/docs.git synced 2026-07-20 19:35:02 -04:00
Code Issues 490 Packages Projects Releases Wiki Activity

[PR #3948] [MERGED] ci: opt-in auto-request reviewers via OWNERS marker #3955

New Issue
Closed
opened 2026-06-05 18:53:42 -04:00 by yindo · 0 comments
yindo commented 2026-06-05 18:53:42 -04:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/3948
Author: @mdrxy
Created: 5/11/2026
Status: ✅ Merged
Merged: 5/11/2026
Merged by: @mdrxy

Base: main ← Head: open-swe/owners-auto-request

📝 Commits (2)

  • 869e90e ci: opt-in auto-request reviewers via OWNERS marker
  • ff66d84 Merge branch 'main' into open-swe/owners-auto-request

📊 Changes

2 files changed (+81 additions, -10 deletions)

View changed files

📝 .github/OWNERS (+11 -1)
📝 .github/workflows/pr-welcome-comment.yml (+70 -9)

📄 Description

Description

Extends .github/workflows/pr-welcome-comment.yml with an opt-in
# auto-request[: @user ...] marker on .github/OWNERS rules so the
workflow can call requestReviewers for opted-in owners on matching
PRs.

This is needed because the existing welcome comment only tells authors
who owns the touched docs areas. It does not create a GitHub review
request, and the owner handles in that comment are formatted as code, so
they are not reliable mention notifications. The new marker creates an
actual requested reviewer entry while keeping the behavior opt-in per
OWNERS rule.

Wires up @mdrxy for /src/oss/deepagents/cli/.

Release Note

none

Test Plan

  • After merge, open a non-draft PR touching a file under
    src/oss/deepagents/cli/ from a non-owner account and confirm
    @mdrxy is auto-requested as a reviewer, and @npentrel is not.
  • Open an unrelated PR, for example touching src/langsmith/, and
    confirm no extra reviewers are auto-requested beyond existing
    behavior.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langchain-ai/docs/pull/3948 **Author:** [@mdrxy](https://github.com/mdrxy) **Created:** 5/11/2026 **Status:** ✅ Merged **Merged:** 5/11/2026 **Merged by:** [@mdrxy](https://github.com/mdrxy) **Base:** `main` ← **Head:** `open-swe/owners-auto-request` --- ### 📝 Commits (2) - [`869e90e`](https://github.com/langchain-ai/docs/commit/869e90e5ed47bb7cb7b68030cadc415672e7b36f) ci: opt-in auto-request reviewers via OWNERS marker - [`ff66d84`](https://github.com/langchain-ai/docs/commit/ff66d84524b5fb9815288f899ddac13dd9b49a4d) Merge branch 'main' into open-swe/owners-auto-request ### 📊 Changes **2 files changed** (+81 additions, -10 deletions) <details> <summary>View changed files</summary> 📝 `.github/OWNERS` (+11 -1) 📝 `.github/workflows/pr-welcome-comment.yml` (+70 -9) </details> ### 📄 Description ## Description Extends `.github/workflows/pr-welcome-comment.yml` with an opt-in `# auto-request[: @user ...]` marker on `.github/OWNERS` rules so the workflow can call `requestReviewers` for opted-in owners on matching PRs. This is needed because the existing welcome comment only tells authors who owns the touched docs areas. It does not create a GitHub review request, and the owner handles in that comment are formatted as code, so they are not reliable mention notifications. The new marker creates an actual requested reviewer entry while keeping the behavior opt-in per OWNERS rule. Wires up `@mdrxy` for `/src/oss/deepagents/cli/`. ## Release Note none ## Test Plan - [ ] After merge, open a non-draft PR touching a file under `src/oss/deepagents/cli/` from a non-owner account and confirm `@mdrxy` is auto-requested as a reviewer, and `@npentrel` is not. - [ ] Open an unrelated PR, for example touching `src/langsmith/`, and confirm no extra reviewers are auto-requested beyond existing behavior. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-06-05 18:53:42 -04:00
yindo closed this issue 2026-06-05 18:53:42 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
deepagents
docs-infra
external
external
help wanted
integration
internal
internal
javascript
js/ts
langchain
langgraph
langsmith
needs-title
pull-request
Mirrored from GitHub Pull Request
 python
reference
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/docs#3955
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?