master -> main

Justin Chu
2024-11-22 08:39:38 -08:00
parent a52a7414d7
commit ed0400a93f

@ -66,11 +66,11 @@ On Azure Linux:
sudo dnf install glibc-devel kernel-headers
```
Then see the instructions in PyTorch's [README](https://github.com/pytorch/pytorch/blob/master/README.md#from-source).
Then see the instructions in PyTorch's [README](https://github.com/pytorch/pytorch/blob/main/README.md).
#### Optional build tips
[PyTorch C++ development tips](https://github.com/pytorch/pytorch/blob/master/CONTRIBUTING.md#c-development-tips).
[PyTorch C++ development tips](https://github.com/pytorch/pytorch/blob/main/CONTRIBUTING.md#c-development-tips).
[Use direnv for Anaconda environment selection](https://github.com/direnv/direnv/wiki/Python#anaconda).
@ -258,7 +258,7 @@ You can then set breakpoints in the c++ source and run the debugger in VS Code.
## Pull requests
PRs should be opened directly against master. PRs can be directly merged into master as long as it satisfies the [ONNX merge rule](https://github.com/pytorch/pytorch/blob/master/.github/merge_rules.yaml#L1):
PRs should be opened directly against main. PRs can be directly merged into main long as it satisfies the [ONNX merge rule](https://github.com/pytorch/pytorch/blob/main/.github/merge_rules.yaml#L1):
* Approved by one of torch.onnx developers listed in `approved_by` section.
* All modified files fall under the `patterns` section.
@ -268,12 +268,12 @@ Pay special attention to the following GitHub checks:
* Has "onnx" in the name, which runs ONNX related tests.
* Has "Lint" in the name, which does code format checks.
Regarding other failing checks: if you are certain the failure is unrelated to your change, try rebasing on master. Often these failures are caused by a branch being out of sync with master.
You can ignore the failing check if it is a regression in master. This can be verified by checking if master is also failing from [CI HUD](https://hud.pytorch.org/ci/pytorch/pytorch/master).
Regarding other failing checks: if you are certain the failure is unrelated to your change, try rebasing on main. Often these failures are caused by a branch being out of sync with main.
You can ignore the failing check if it is a regression in main. This can be verified by checking if main is also failing from [CI HUD](https://hud.pytorch.org/ci/pytorch/pytorch/main).
**To merge your pull request, comment on the PR `@pytorchbot merge`.** (doc [[Bot commands|]])
If you make changes to non-ONNX related code, i.e. files outside of [ONNX merge rule](https://github.com/pytorch/pytorch/blob/master/.github/merge_rules.yaml#L1), please note the PR will require additional reviews from people outside of torch.onnx developers, and will take a longer process to merge into master. In this case, pytorchbot will not be able to merge the pull request. It will leave a comment like "Merge failed due to PR XXX does not match merge rules". Please label the pull request with `onnx-needs-import`.
If you make changes to non-ONNX related code, i.e. files outside of [ONNX merge rule](https://github.com/pytorch/pytorch/blob/main/.github/merge_rules.yaml#L1), please note the PR will require additional reviews from people outside of torch.onnx developers, and will take a longer process to merge into main. In this case, pytorchbot will not be able to merge the pull request. It will leave a comment like "Merge failed due to PR XXX does not match merge rules". Please label the pull request with `onnx-needs-import`.
See [GitHub pull request workflow](https://docs.github.com/en/get-started/quickstart/github-flow).
@ -322,7 +322,7 @@ Set the environment variable `TORCH_LOGS="onnx_diagnostics"` to capture detailed
# Links
* [User-facing docs](https://pytorch.org/docs/master/onnx.html).
* [User-facing docs](https://pytorch.org/docs/main/onnx.html).
## Relevant parts of PyTorch repo