Bumping this. I also have Slack notifications as my primary use case, but this could be generally-useful, as I proposed to @fehersanyi-bitrise:
The feature I’m requesting is simply an environment variable that is present when someone manually triggers a build, which includes information about the Bitrise user that triggered it
This can then be used in workflow scripts, for example: a
BITRISE_TRIGGER_SOURCE environment variable that could be “0” for “Webhook”-triggered builds, “1” for “Scheduled”, maybe “3” for manually-launched workflows, etc.
In the manual case, Bitrise could also provide other env vars, e.g.
BITRISE_TRIGGER_EMAIL, etc., which would respectively include the username, email address, etc. of the user who launched the workflow.
Beyond notification routing, this information could also be used as input to build steps that might generate custom artifacts, apps, etc.