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

removed -a as it's not available rn

Jane (Yuan) Xu
2022-06-03 10:31:55 -04:00
parent 5802cb7d3b
commit f842acf8be
1 changed files with 1 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
Bot-commands.md

@ -20,12 +20,11 @@ By default, the Lint and pull workflows should run on every push to your pull re
We are in the process of prototyping our GitHub First initiative, which will allow certain pull requests based on the upstream repo (not a fork) to be merged through GitHub first, then imported internally into Meta. The requirements for such PRs are described in [our merge rules](https://github.com/pytorch/pytorch/blob/master/.github/merge_rules.json) where files fitting the specified patterns approved by the specified maintainers are allowed to merge directly with the following comment:
```
usage: @pytorchbot merge [-g] [-a] [-f]
usage: @pytorchbot merge [-g] [-f]
optional arguments:
-g, --green Merge when required status checks pass. Currently, we only
require lint and builds to pass.
-a, --all-green Merge when all status checks pass
-f, --force Merge without checking anything. ONLY USE THIS FOR CRITICAL
FAILURES.
```