95% we do have this, 5% sure it could be merged with an existing issue

• If you set a trigger, we'll go off that

• You can enable PR deploys in project settings under environment (or through the palette)
  Otherwise, if you're wondering if we can wait until all checks pass before rolling out, that's "Wait for CI before deploying" (https://railway.canny.io/admin/feedback/feature-requests/p/wait-for-ci-before-deploying?boards=feature-requests&search=wait+for).
  Let me know either way

95% we do have this, 5% sure it could be merged with an existing issue

• If you set a trigger, we'll go off that

• You can enable PR deploys in project settings under environment (or through the palette)
  Otherwise, if you're wondering if we can wait until all checks pass before rolling out, that's "Wait for CI before deploying" (https://railway.canny.io/admin/feedback/feature-requests/p/wait-for-ci-before-deploying?boards=feature-requests&search=wait+for).
  Let me know either way

Jake Cooper: Looks like I referenced the wrong GitHub API. What I really meant is supporting commit statuses (https://docs.github.com/en/rest/reference/commits#commit-statuses).
"The status API allows external services to mark commits with an error, failure, pending, or success state, which is then reflected in pull requests involving those commits."
This is useful for quickly checking if a deployment of a commit on the main/master branch has passed or failed directly on GitHub.