Akshay Gupta

Currently there's basically 0 error handling for the Slack integration. Since the integration is simple and does not really fail, we've punted on this for now.

"External Deployments" or in other words, deployments that do not fit into the list of deployment integrations possible in tramline are handle by simple view hacks in the codebase. If...

See https://sentry.io/organizations/tramline/issues/3547992791/?project=6541299

Allow only certain people to start a hotfix release

Describe how branches move etc. Also describe the work that happens before and after the strategies diagrammatically, maybe.

So users can directly download from releases page. Inside `Assets`, example: https://github.com/tramlinehq/ueno/releases/tag/v78.16.1

This can act as a cheap "automation" middle-ground before a full-fledged cron-like scheduling functionality

Google PlayStore: * With multiple deployments, PlayStore should only be deployed to once if there are multiple deployment channels as play store (with different tracks). This poses a design problem...

Github has a webhook event to handle [this](https://docs.github.com/en/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#installation). Others might too.

Changes cannot be sent for review automatically from API

2

This error from Play Store while using the API: > Edit could not be committed due to an error. Changes cannot be sent for review automatically. Please set the query...