Hi @BrightRan Thanks for your response and help with this issue. I got an official reply from GitHub support (Feb 28, 11:34PM UTC - 20 days after the incident): Due to an issue with our backend systems, less than 0.1% of organizations using Actions saw a delay in workflows starting between 02-13-2020 and 02-14-2020. Your organization was identified as one of the potentially impacted ones due to this issue. The impact was within our SLO (Service Level Objective) and we did not update the public status of Actions. We know how important the reliability of our service is for our customers, and we take this responsibility very seriously and apologize for these disruptions to run workflows. Our engineering team deployed fixes to mitigate on 02-13-2020, a full fix at 02-14-2020 11:00 UTC after which the backlog of jobs started processing. We have taken steps to ensure we identify these issues and communicate early to the impacted customers. Our hope is that for these future incidents we can get an update from GitHub, it's just a very unfortunate situation for us but hopeful in the fact that GitHub can improve from this. Regards, Chris
... View more
We have experienced the same issue for GitHub Actions and reached out to GitHub about this. The suggestion they gave to us was to use the suites API (https://developer.github.com/v3/checks/suites/) instead of statuses Other CI tools such as CircleCI and Jenkins rely on statuses but not GitHub Actions it seems. You can create your own status by pushing to the statuses API itself if necessary (bit of a hack though) The example repository I showed them was here: https://github.com/cfarrend/github-status-checks From GitHub Support: Rather than using the endpoint for listing statuses for a specific ref: https://developer.github.com/v3/repos/statuses/#list-statuses-for-a-specific-ref We suggest using this endpoint for listing the check suites for a specific ref, since GitHub Actions creates check suites and check runs to reflect those job statuses (and not commit statuses): https://developer.github.com/v3/checks/suites/#list-check-suites-for-a-specific-ref Here's an example using curl (https://curl.haxx.se) for fetching a list of check suites for the first commit, b147efab0447fe54c7ea567508ccfabb555816f4: curl -H "Accept: application/vnd.github.antiope-preview+json" "https://api.github.com/repos/cfarrend/github-status-checks/commits/b147efab0447fe54c7ea567508ccfabb555816f4/check-suites"
# ... There's also an endpoint for fetching a list of check runs for a specific ref: https://developer.github.com/v3/checks/runs/#list-check-runs-for-a-specific-ref Here's another example curl request: curl -H "Accept: application/vnd.github.antiope-preview+json" "https://api.github.com/repos/cfarrend/github-status-checks/commits/b147efab0447fe54c7ea567508ccfabb555816f4/check-runs"
... View more