Skip to content
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

Add General Project Policies #87385

Closed
wants to merge 4 commits into from
Closed

Conversation

svekars
Copy link
Contributor

@svekars svekars commented Oct 20, 2022

Add General Project Policies to the Governance page

Add General Project Policies to the Governance page
@pytorch-bot
Copy link

pytorch-bot bot commented Oct 20, 2022

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/87385

Note: Links to docs will display an error until the docs builds have been completed.

❌ 3 Failures

As of commit 8208186:

The following jobs have failed:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@svekars svekars requested a review from orionr October 20, 2022 19:41
Copy link
Contributor

@orionr orionr left a comment

Choose a reason for hiding this comment

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

LGTM!

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Oct 20, 2022
@svekars
Copy link
Contributor Author

svekars commented Oct 20, 2022

@pytorchbot merge -f "Doc update"

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

@github-actions
Copy link

Hey @svekars.
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.

atalman pushed a commit to atalman/pytorch that referenced this pull request Oct 24, 2022
Add General Project Policies to the Governance page

Pull Request resolved: pytorch#87385
Approved by: https://github.com/orionr
atalman added a commit that referenced this pull request Oct 24, 2022
Add General Project Policies to the Governance page

Pull Request resolved: #87385
Approved by: https://github.com/orionr

Co-authored-by: Svetlana Karslioglu <svekars@fb.com>
sgrigory pushed a commit to sgrigory/pytorch that referenced this pull request Oct 28, 2022
Add General Project Policies to the Governance page

Pull Request resolved: pytorch#87385
Approved by: https://github.com/orionr
@github-actions github-actions bot deleted the update-governance-page-gen-policies branch April 21, 2024 01:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ciflow/trunk Trigger trunk jobs on your pull request Merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants