frozenleaves/pytorch
1
0
Fork 0
mirror of https://github.com/pytorch/pytorch.git synced 2025-10-20 12:54:11 +08:00
Code Issues Packages Projects Releases Wiki Activity

Add branch change name for composite action (#101309)

Browse Source 
Mention in release runbook, that composite workflow should reference release branch rather than trunk

Pull Request resolved: https://github.com/pytorch/pytorch/pull/101309
Approved by: https://github.com/atalman
This commit is contained in:
Nikita Shulga
2023-05-12 21:50:12 +00:00
committed by PyTorch MergeBot
parent 47c99e3a1c
commit 816400a294
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
RELEASE.md
View File

@ -108,6 +108,8 @@ them:
* Example: https://github.com/pytorch/pytorch/pull/77983 and https://github.com/pytorch/pytorch/pull/77986
* A release branches should also be created in [`pytorch/xla`](https://github.com/pytorch/xla) and [`pytorch/builder`](https://github.com/pytorch/builder) repos and pinned in `pytorch/pytorch`
* Example: https://github.com/pytorch/pytorch/pull/86290 and https://github.com/pytorch/pytorch/pull/90506
* Update branch used in composite actions from trunk to release (for example, can be done by running `for i in .github/workflows/*.yml; do sed -i -e s#@master#@release/2.0# $i; done`
* Example: https://github.com/pytorch/pytorch/commit/51b42d98d696a9a474bc69f9a4c755058809542f
These are examples of changes that should be made to the *default* branch after a release branch is cut