Skip to content

[GHF] Adding James Reed to Merge Rules superusers #74758

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.

Sign up for GitHub

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

Jump to bottom
Closed
osalpekar wants to merge 1 commit into from
Closed

[GHF] Adding James Reed to Merge Rules superusers #74758

osalpekar wants to merge 1 commit into from

Conversation

@osalpekar
Copy link
Member

@osalpekar osalpekar commented Mar 25, 2022

Summary: See Title

Test Plan: NA

Differential Revision: D35147762

@osalpekar @facebook-github-bot
[GHF] Adding James Reed to Merge Rules superusers
db8a46f 
Summary: See Title

Test Plan: NA

Differential Revision: D35147762

fbshipit-source-id: bd493f550841c8911ffaa4327861ab945cec6044
@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Mar 25, 2022 •
edited
Loading

🔗 Helpful links

💊 CI failures summary and remediations

As of commit db8a46f (more details on the Dr. CI page):

💚 💚 Looks good so far! There are no failures yet. 💚 💚

This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Mar 25, 2022

This pull request was exported from Phabricator. Differential Revision: D35147762

facebook-github-bot pushed a commit that referenced this pull request Mar 25, 2022
@osalpekar @facebook-github-bot
[GHF] Adding James Reed to Merge Rules superusers (#74758)
190f429 
Summary:
Pull Request resolved: #74758

See Title

Test Plan: NA

Reviewed By: jamesr66a

Differential Revision: D35147762

fbshipit-source-id: 34572bfb3aef5e14a06fe27dc3008308b40bdc34
@github-actions
Copy link
Contributor

github-actions bot commented Mar 25, 2022

Hey @osalpekar.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.

@WBobby WBobby mentioned this pull request Aug 17, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jamesr66a jamesr66a jamesr66a approved these changes

@seemethere seemethere Awaiting requested review from seemethere

@janeyx99 janeyx99 Awaiting requested review from janeyx99

@atalman atalman Awaiting requested review from atalman

Assignees

No one assigned

Labels

cla signed fb-exported

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@osalpekar @facebook-github-bot @jamesr66a