Comment 1 for bug 1660821

Here are the options I see:
- We can manually trigger github-merge-branches on the rare occasion that there is a bless.
- The update-outcome script can trigger github-merge-branches when there is a bless.
  - This will happen before the reports site is updated
  - We may need to work to prevent github-merge-branches from being called multiple times
  - This prevents us from using outcome analyser in determining a bless
- The get-s3-ci-results script can trigger github-merge-branches when there is a bless
  - This will happen roughly simultaneously with updating the report
  - We may need to work to prevent github-merge-branches from being called multiple times
  - This allows us to use outcome analyser in determining a bless
- We can add a REST API to the reports site.
  - github-merge-branches would use the API to determine the last blessed build
  - github-merge-branches would run periodically, and exit early most of the time.

1. The update-outcome script can trigger