My company has over a dozen microservices that we release based on a tag. This is a very manual process with SlashDeploy currently. Would it be possible to allow a comma separated list of repos in the /deploy command. For example, then we could do:

/deploy owner/repo1@refs/tags/v1.2.0,owner/repo2@refs/tags/v1.2.0,owner/repo3@refs/tags/v1.2.0 to production

Alternatively, a new predicate could be added for tag. For example an at <tag> predicate:

/deploy owner/repo1 at v1.2.0 to production

Combining with the comma-separated list of repos we would have:

/deploy owner/repo1,owner/repo2,owner/repo3 at v1.2.0 to production

That would be a very streamlined way to release a specific version of multiple repos.

SlashDeploy already follows the GitHub permissions, however, it's not clear which repositories I can deploy to ahead of time. It'd be great to /deploy list repositories I have access to. Alternatively, it could also be combined with /deploy where, but without providing a repo.

On-premise version of SlashDeploy, installable alongside GitHub Enterprise.

Document some examples of deployment workflows with various providers:

• GitHub Actions
• ElasticBeanstalk
• Capistrano
• BuildKite
• Drone.io
• CircleCI

Add support for deployment queues on a per-environment basis. For instance, a user could queue herself up for a deploy on a certain environment, and once the environment is free (deployed and unlocked) it will be locked by the queued user and she gets notified that it's ready.

It would be nice to have a customizable help/how message to teach new users how to /deploy. What do you think of a an entry in .slashdeploy.yml that's markdown that's access via /deploy usage or similar

it would be useful to customize deploy payloads with each deploy. We have seeding tasks that happen after deploys to test environments. If we could pass some payload context we could expose to seed or not as part of the /deploy workflow.

One other thing that would be good is being able to specify which branch slashdeploy should be looking for the config file from. I know it's currently whatever is the default branch in Github but would be nice to be able to specify through the UI. Even being able to just configure through the UI would be nice.

Get deployment metrics/graphs right inside Slack for a given period. Possible charts:

• Velocity - Number of deployments per week/month
• Leaderboard - Top deployers per week/month
• Quality - Success/failure ratio per week/month

GitHub Checks provide far more detailed view of what and why the check has failed. It'd be great to show this information in the Slack when deploy stops due to a failed check.

At the moment, trying to manually deploy to an auto-deployed environment results in the warning below. So, make it possible to configure SlashDeploy to silence such a warning.

we have a mono repo (i.e. one GitHub repo that contains multiple independently versioned packages) project that we would like to use with the service
ideally each individual package would be able to have its own .slashdeploy.yml config
is this something that the service can support?

Received feedback:

how come commands aren't echoed in the channels?

Currently, only production environment deployments will echo back commands to channels for others to see. It'd be great to enable echoing back in the .slashdeploy.yml configuration file, on a per-environment basis.

I know you can specify the ref for auto_deploy however when running a command like
/deploy to development
I want the default branch to be development however it is master.

I've read through https://docs.getslashdeploy.com/config and didn't find anything

Hi there, I suddenly have this problem and ended up here.

as you can see ref which is I used to use github.ref from github action is missing from last night, below screenshot is from echo ${{ toJson(github) }} on Github Action.

Also, I checked the Github Deployment detail with id, sha and ref are same, I think ref should be something like refs/head/master.

please take a look for me, thanks!

Seems like GitHub API (https://developer.github.com/v3/repos/deployments/#failed-commit-status-checks) treats “neutral” as a failure and hence raises a 409 Conflict error which SlashDeploy bubbles up. Neutral status runs should be ok for deploys.

It would be nice if it was possible to deploy per PR environments to preview changes. This is mostly useful to validate frontend changes, but also check that database migrations and new features are working as expected.

You might want to draw some inspiration from https://deliverybot.dev/

Is it possible to disable locking on particular environments? We're trying to use SlashDeploy to execute automated e2e tests