This covers the real thing in between getting the "issue" webhook data
and uploading the image to the S3 server, and hence issue-scan,
image-refresh, image-create, S3 image credentials, etc.
Extend mock-github for the operations that image-refresh does, like
converting an issue to a pull, posting test statuses, etc. These aren't
asserted: it's possible in principle with keeping state in the mock,
but these aren't the parts that are sensitive to us changing our bots
infrastructure. Also, these are better done in bots' unittests than this
integration test.
This covers the real thing in between getting the "issue" webhook data and uploading the image to the S3 server, and hence
issue-scan,image-refresh,image-create, S3 image credentials, etc.Extend mock-github for the operations that
image-refreshdoes, like converting an issue to a pull, posting test statuses, etc. These aren't asserted: it's possible in principle with keeping state in the mock, but these aren't the parts that are sensitive to us changing our bots infrastructure. Also, these are better done in bots' unittests than this integration test.TODO: