viable/strict disclaimer

clee2000
2022-05-26 13:17:46 -07:00
parent 210999bd8c
commit 6574cf2b05

@ -53,7 +53,7 @@ Rebasing is useful you're reviewing an older PR and want to get new signal: you
We also have the following flags:
-s, -stable, -viableStrict: rebase the PR to the viable/strict branch instead of master. The viable/strict branch contains all commits on pytorch/pytorch that are green and stable (i.e. it passes all of the CI checks).
-s, -stable, -viableStrict: rebase the PR to the viable/strict branch instead of master. The viable/strict branch contains all commits on pytorch/pytorch that are green and stable (i.e. it passes all of the CI checks). (disclaimer: if you are based off a commit that is newer that viable/strict, like master, then rebasing to viable/strict will not do anything)
Examples:
```