Stale check runs

I’m planning to create an app that uses the Check Runs API. The checks performed on the code will not be automated, and thus could take a very long time to complete. I noticed that if a check is in progress for more than 14 days GitHub will automatically mark the run as stale (https://developer.github.com/v3/checks/runs/). I have a couple of questions about stale check runs:

  1. Can I still update the run status once it is marked as stale?
  2. If the check is required for merging into a protected branch, will the check be still be required after it is marked as stale?

:wave: hello there @danthedaniel, and welcome to the GitHub Support Community! :tada:

  1. Can I still update the run status once it is marked as stale?

Once a check run transitions from the in_progress state to completed state, it’s not possible to modify its status nor its conclusion further. Also, only GitHub can change a check run conclusion to stale as documented in the parameters section for creating a check run.

  1. If the check is required for merging into a protected branch, will the check be still be required after it is marked as stale?

Yes. If a check is required as a part of a protected branch’s settings, the check must pass as noted in About required status checks. A check run with a stale conclusion is not the same as a check run with a success conclusion. I hope this helps!

1 Like

But what about when a check run transitions from in_progress to stale? Can I modify the status then?