(Github) Status Checks for Deployments

What problem will this feature address?

Currently, the deployment status is not visible directly in GitHub. This makes it difficult to use deployment results as part of the repository’s quality gates.

Having deployment statuses available in GitHub would be especially valuable for:

• Blocking the merge of branches when deployments fail
• Enforcing safeguards in preview deployments
• Handling automatically generated or auto-merged pull requests (e.g. from Dependabot, Renovate, or similar tools)

Without deployment visibility, failed preview or staging deployments can go unnoticed, potentially allowing unstable changes to be merged.

Describe the solution you'd like

The deployment status should be visible in GitHub and reflect the current state of the deployment lifecycle. At a minimum, it should indicate whether a deployment is:

• Queued (if feasible)
• Currently running
• Successful
• Failed

This information should be available in a way that allows it to be used for branch protection rules and merge checks.

Describe alternatives you've considered

One alternative would be to build and deploy the project directly using GitHub Actions. However, this approach is not ideal for several reasons:

• It leads to unnecessary consumption of CI resources
• It is not practical in certain scenarios, such as builds or deployments that require sensitive secrets or access to restricted infrastructure

As a result, relying solely on GitHub Actions for this purpose is not a viable solution in all cases.

Additional context

No response

Will you send a PR to implement it?

Yes

No files, tests, or entry points are named in the issue. Start by tracing how the deployment lifecycle is represented and where GitHub integration is handled. Done means deployment states are visible in GitHub and usable as branch protection or merge checks.