Skip to content
Reoclo Reoclo Reoclo Docs

Deployment status on GitHub and Gitea

Every deployment of a repository-backed application posts its result back to your git provider.

Commit status

Section titled “Commit status”

Reoclo posts a commit status with the context reoclo/deploy/<app-slug> on every deployment. The status reads pending while the deployment runs. It reads success, failure, or error when the deployment finishes. Reoclo posts error when you cancel the deployment.

The status includes a Details link to the deployment’s page in the Reoclo dashboard.

GitHub and Gitea both show this status on the commit, the pull request, and the branch.

GitHub Deployments

Section titled “GitHub Deployments”

On GitHub, Reoclo also creates a GitHub Deployment for each application. The deployment’s environment name matches the application’s slug. Reoclo marks the environment as a production environment.

The deployment’s status reads in_progress while the deployment runs, then success, failure, or error.

Find the deployment in your repository’s Environments panel. Each entry has a View deployment link to the same page in the Reoclo dashboard.

Gitea has no Deployments API. A Gitea repository gets the commit status only.

Turning a surface off

Section titled “Turning a surface off”

Set these keys in reoclo.yml to turn a surface off for one application.

ci:
  report_status: true        # post a commit status (reoclo/deploy/<app>) for each deployment
  report_deployment: true    # on GitHub, also create a Deployment in the Environments panel

Set report_status to false to stop the commit status. Set report_deployment to false to stop the GitHub Deployment.

See the reoclo.yml reference.

GitHub App permissions Reoclo needs

Section titled “GitHub App permissions Reoclo needs”

Reoclo needs these permissions to post deployment status:

  • Commit statuses: Read and write
  • Deployments: Read and write
  • Checks: Read

An organization owner must accept a new permission request before Reoclo can use it. Until an owner accepts the request, Reoclo logs the refused post. The deployment itself still finishes.

When your git provider is unavailable

Section titled “When your git provider is unavailable”

A git provider outage never blocks a deployment. Reoclo still builds, deploys, and runs your application. Reoclo only fails to post the status update.

Next Steps

Section titled “Next Steps”