Tobias Henkel 9fa93fdefa Use combined status for Github status checks ... When checking the required status checks we currently get all statuses and get the successful of them. However Github returns all historic status changes there. So a change that get a successful check, then a recheck and then a failed check still enters the gate but will be prohibited by Github to merge in the end. However github also offers us a combined status call that only returns the current state of the statuses. Using this fixes the issue. Change-Id: Iec3b2a3dfc8626870381604badd40de71e7257b9		2018-12-07 09:17:03 +01:00
..
fixtures	Merge "Set relative priority of node requests"	2018-11-30 15:24:56 +00:00
nodepool	Set relative priority of node requests	2018-11-30 12:50:34 +01:00
remote	Don't do live streaming in loops	2018-11-05 22:21:38 +01:00
unit	Use combined status for Github status checks	2018-12-07 09:17:03 +01:00
__init__.py	Add non-voting jobs.	2012-08-23 23:20:09 +00:00
base.py	Merge "Set relative priority of node requests"	2018-11-30 15:24:56 +00:00
encrypt_secret.py	Make tests' encrypt_secret.py work with python3	2017-10-19 18:09:57 +00:00
fakegithub.py	Use combined status for Github status checks	2018-12-07 09:17:03 +01:00
make_playbooks.py	Use libyaml if possible	2017-04-04 11:49:05 -07:00
print_layout.py	Do not add implied branch matchers in project-templates	2017-09-30 10:19:07 -07:00