James E. Blair 9a0d4df0a3 Log more information about what events trigger a reconfig ... A tenant reconfiguration might be caused by a branch creation, deletion, or change to files. Cause TriggerEvents to repr themselves with flags indicating which of those are true. Have the GithubTriggerEvent also repr itself with the associated delivery id for easier tracing. Finally, have the scheduler log these events when performing a tenant reconfiguration so we can see all the info. Change-Id: I2cfc7615dfb3533aeb9d42b009cc67ce88a5ee48		2018-06-22 12:48:51 +02:00
..
__init__.py	Status branch protection checking for github	2018-06-04 15:47:01 +02:00
githubconnection.py	Log more information about what events trigger a reconfig	2018-06-22 12:48:51 +02:00
githubmodel.py	Log more information about what events trigger a reconfig	2018-06-22 12:48:51 +02:00
githubreporter.py	Status branch protection checking for github	2018-06-04 15:47:01 +02:00
githubsource.py	Merge "Limit search scope of getChangesDependingOn to tenant"	2018-06-02 06:54:22 +00:00
githubtrigger.py	Use util functions to make lists of things	2017-05-30 14:53:46 -07:00