Deployment+Statuses vs Actions+Checks

Hi there - I’m converting our Jenkins workflows into Github Actions and think I’m struggling with the conceptual difference between Statuses and Checks… They seem like they’re pretty close, but I’ve not found anything in the docs directly comparing them. Are Checks intended to eventually replace Statuses, or are they intended to live alongside each other with different use cases?

Our old workflow is:

  • a developer runs our deployment tool (capistrano) on their laptop
  • it uses Octokit to create the deployment on github, passing required_contexts: ["jenkins"]
  • if that reports a conflict, it means that jenkins’ tests are still pending/failed, so prompt the developer to do something about that
  • otherwise, deploy the code, and update the deployment status on failure/success

I’ve got all our tests running in Github Actions, and can see that they create Checks, but not Statuses, which surprised me. I need a Status to be able to use required_contexts against it, right?

I’m sure I could manually set up the statuses during the action using the REST API, but that seems like going against the grain to suite our old workflow. Is there a better Action/Check-based way to manage deployments?

1 Like

Is there a more suitable place I might ask this?