All deployments are not created equal, but you'd never know it from your Slack channel notifications. In reality, some deployments you really care about, as they contain things like API changes or database migrations, and you want that information to surface. We created tags in Sleuth for this very reason.
Out of the box, Sleuth matches files in your deployment with known patterns, and if any are found, tags your deployments automatically. For example, if your deployment contained a file in a "migrations" directory, it will be tagged with #migration.
To customize the tags and their patterns, you can edit the .sleuth/TAGS file in your repo. This file is similar to the GitHub CODEOWNERS file format. You can also provide tags in the HTTP POST if that is how you register your deployments.
For more information, see the documentation, and as always, please let us know how it works for you and other ideas on how Sleuth can better categorize your deployments.