Deploy

    
/deploy {env} {revision}
    

Sends a notification to GitHub Actions for said repository with a repository dispatch event. I take the env as use it as the type of deployment sent to GitHub Actions.

For example /deploy production 1.2.3 would send this payload to the repository being tracked by the Slack channel in which the command was called:

    
{
  "event_type": "production-deployment",
  "client_payload": {
    "ref": "1.2.3"
  }
}
    

DeployBot does no validation that production-deployment is a listened-for GitHub Action. In fact, DeployBot does no validation other than:

1. Verify a repository is tracked in the Slack channel where the command was called
2. Verify DeployBot has access to the GitHub repository

Follow Repository

    
/deploy-follow {owner/repo} {github-access-token}
    

Tracks and facilitates deployments for a GitHub repository in a Slack channel. Only one repository is trackable per Slack channel.

A github access token is required.

If DeployBot is already following a repository, it'll report back in the Slack channel as such. Following a new or different repository requires unfollowing the current and following the new target.

With each new, valid follow request, DeployBot ensures it can access the GitHub repository.

Unfollow Repository

    
/deploy-unfollow {owner/repo}
    

Todo

List Deployments for Slack Channel

    
/deploy-list {?env}
    

Todo

Help

    
/deploy-help
    

Todo