-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Add merge_rule for "functorch" module #96657
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This PR enables our non-meta contributors to be able to approve "functorch" PRs without intervention from meta contributors. A PR is deemed a "functorch" PR if it matches one of the patterns in merge_rules.yaml. These patterns are definitely not exhaustive (we modify core pytorch pieces quite often), but should be a good starting point. [ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/96657
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 10b36a4: This comment was automatically generated by Dr. CI and updates every 15 minutes. |
cc @kshitij12345 @srossross when this PR gets merged, you folks will be able to approve (and merge) functorch PRs without needing someone from meta also approve the PR. |
This PR enables our non-meta contributors to be able to approve "functorch" PRs without intervention from meta contributors. A PR is deemed a "functorch" PR if it matches one of the patterns in merge_rules.yaml. These patterns are definitely not exhaustive (we modify core pytorch pieces quite often), but should be a good starting point. [ghstack-poisoned]
This PR enables our non-meta contributors to be able to approve "functorch" PRs without intervention from meta contributors. A PR is deemed a "functorch" PR if it matches one of the patterns in merge_rules.yaml. These patterns are definitely not exhaustive (we modify core pytorch pieces quite often), but should be a good starting point. ghstack-source-id: d7e4ede Pull Request resolved: #96657
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SGTM!
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
This PR enables our non-meta contributors to be able to approve "functorch" PRs without intervention from meta contributors. A PR is deemed a "functorch" PR if it matches one of the patterns in merge_rules.yaml. These patterns are definitely not exhaustive (we modify core pytorch pieces quite often), but should be a good starting point. Pull Request resolved: pytorch/pytorch#96657 Approved by: https://github.com/albanD
This PR enables our non-meta contributors to be able to approve "functorch" PRs without intervention from meta contributors. A PR is deemed a "functorch" PR if it matches one of the patterns in merge_rules.yaml. These patterns are definitely not exhaustive (we modify core pytorch pieces quite often), but should be a good starting point. Pull Request resolved: pytorch/pytorch#96657 Approved by: https://github.com/albanD
Stack from ghstack:
This PR enables our non-meta contributors to be able to approve
"functorch" PRs without intervention from meta contributors.
A PR is deemed a "functorch" PR if it matches one of the patterns in
merge_rules.yaml. These patterns are definitely not exhaustive
(we modify core pytorch pieces quite often), but should be a good starting
point.