Chiebot-Mirror/grpc - grpc - Gitea: Git with a cup of tea

49390 Commits

276 Branches

378 Tags

1.2 GiB

Tag: Branch: Tree: c5b7d4101d

Commit Graph

Author	SHA1	Message	Date
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	3 years ago

Author

SHA1

Message

Date

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

3 years ago

1 Commits (c5b7d4101dd11a9d9dbe1735d537df331fb84aab)