Skip to content

Conversation

@mdrxy
Copy link
Member

@mdrxy mdrxy commented Nov 15, 2025

Ready to go, but before it will work we need to:

  1. Create a GitHub app and install it in our org/on this repo. It needs permissions to read org membership and to write to PR/issues (to add the labels).
  2. Add these secrets to this repo:
  • ORG_MEMBERSHIP_APP_ID
  • ORG_MEMBERSHIP_APP_PRIVATE_KEY

@github-actions github-actions bot added the ci label Nov 15, 2025
@github-actions
Copy link
Contributor

Mintlify preview ID generated: preview-mdrxyt-1763243249-2f1969e

Copy link
Collaborator

@lnhsingh lnhsingh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like tagging external instead of internal fwiw. Might want another eng to do a tech review

@mdrxy mdrxy requested a review from eyurtsev November 17, 2025 16:27
@mdrxy mdrxy requested a review from Copilot November 22, 2025 07:53
Copilot finished reviewing on behalf of mdrxy November 22, 2025 07:55
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds a GitHub Actions workflow to automatically tag issues and pull requests as "external" when they are created by users who are not members of the langchain-ai organization. The workflow uses GitHub's organization membership API to determine if a contributor is internal or external and applies labels accordingly.

Key changes:

  • New automated workflow for contributor classification
  • Supports both GitHub App tokens and Personal Access Tokens for org membership checking
  • Handles both issues and pull requests via separate triggers

@github-actions
Copy link
Contributor

Mintlify preview ID generated: preview-mdrxyt-1763847664-a64f13b

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants