If you received a Slack notification telling that deployment did not start, make sure that:
- The service handling deployment events is working and sending Deployment status updates correctly back to GitHub.
/deploycommands recognize the environment you have defined in the
.slashdeploy.ymlfile, make sure that the configuration file has been pushed to the GitHub's default branch. SlashDeploy syncs up configuration changes only from the default branch.
If you received a Slack notification telling that deployment hung, make sure that all the required status
checkslisted in the
.slashdeploy.ymlfile are not stuck in
pendingstate in GitHub. Try to transition these checks to either
errorand your deployment will likely continue.
If you've configured
channelto receive deployment notifications, but they are still sent as direct messages, make sure that you've invited
@slashdeploybot user to the respective channel. You can use Slack's internal command to do so:
/invite @slashdeploy [channel]