Repository navigation
Enhance workflow to label external PRs - #22381
Merged
Merged
Conversation
Updated the workflow to label external PRs with a community label and refined the exclusion list for authors and bots.
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/22381
Note: Links to docs will display an error until the docs builds have been completed. ✅ You can merge normally! (3 Unrelated Failures)As of commit 4de76db with merge base f5102b8 ( BROKEN TRUNK - The following jobs failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
meta-cla
Bot
added
the
CLA Signed
digantdesai
reviewed
Sep 2, 2026
| "zhenyan-zhang-meta", "silverguo", "harishs88ss", "AlannaBurke", "Doggeral", "laithsakka", "Reubend", "dbort", "huydhn", "mcremon-meta", | ||
| "trivedivivek", "angelayi", "helunwencser", "hsharma35", "zhxchen17", "iseeyuan", "svekars", "nathanaelsee", "dulinriley", | ||
| "jerryzh168", "cmodi-meta", "bigfootjon", "sxu", "ydwu4", "Riandy", "tugsbayasgalan", "bsoyluoglu", "yangw-dev", | ||
| "nil-is-all", "tanvirislam-meta", "cbilgin", "kimishpatel", "psiddh", "digantdesai", "SS-JIA", "ahmtox", "mcr229", |
Contributor
There was a problem hiding this comment.
is there a way to check the org for the author or something easier to maintain?
digantdesai
approved these changes
Sep 2, 2026
nil-is-all
commented
Sep 2, 2026
| ]); | ||
|
|
||
| // List of organization logins (lowercased) to exclude members of | ||
| const excludedOrgs = new Set([ |
Contributor
Author
There was a problem hiding this comment.
@digantdesai yes, I have also added a check for Orgs. The initial version of this automation manually had the author names to exclude (as above). I continued to keep track of individual authors, but can also clean it up to just exclude based on Org if that is easier to maintain
nil-is-all
added a commit
that referenced
this pull request
Sep 28, 2026
Instead of using a Personal Access Token, a GitHub app with read and write permissions for this repo was created. Added the client-id as a variable: EXECUTORCH_TRIAGE_APP_CLIENT_ID and private-key was stored in EXECUTORCH_TRIAGE_APP Part of adding "community: contribution" label to OSS issues and PRs (#22381)
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated the workflow to label external PRs with a community label and refined the exclusion list for authors and bots.
We already have a label - community: contribution. Just updating the workflow which adds community contributed PRs to the Project Board to have this label.