Craig Tiller 8a0b844469 Add a roll-up semi-optional status action (#26939) ... It check status on a pr, and when some set are successful it makes itself successful. If any that it's watching fail, it fails. If the force-merge label is applied, it succeeds. With the plan: we make EasyCLA and probably Sanity, and this one required statuses for merging (i.e. anything that should not be bypassed still gets verified by GitHub) We make every other status that we believe in (so everything but the Google3 presubmits because they're fresh?) something that this script verifies. That lets us do automerge (all things are passing) And if all things are not passing we can use human judgement and apply the force-merge label to bypass these checks... But importantly not the CLA check		2021-08-11 11:20:39 -07:00
..
ISSUE_TEMPLATE	Repo Manager Esun (#26950)	2021-08-09 12:10:08 -07:00
workflows	Add a roll-up semi-optional status action (#26939)	2021-08-11 11:20:39 -07:00
CODEOWNERS	Update a few owners files (#26854)	2021-08-02 21:50:38 -07:00
change_repo_manager.sh	Support MAC	2021-02-12 11:57:10 -08:00
lock.yml	Create lock.yml	2018-09-28 13:49:09 -07:00
mergeable.yml	Update escapes	2019-05-14 23:21:39 -07:00
pull_request_template.md	Repo Manager Esun (#26950)	2021-08-09 12:10:08 -07:00
stale.yml	Stale bot to 90 days	2020-05-18 12:55:55 -07:00