Dunno what I'm doing but this looks right

[watson13j]

🤷‍♂️

[vercel[bot]]

@watson13j is attempting to deploy a commit to a Personal Account owned by undefined on Vercel.

@arkie first needs to authorize it.

[vercel[bot]]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/arkie/dicebot/pqdh79xgd
✅ Preview: https://dicebot-git-ef2c04d7df3a40fcee0a8b83bb2ed17f0c0af728.arkie.vercel.app

[arkie]

First off, thanks for the PR!

I added the Vercel deployment above as an additional command endpoint (in a separately configured app instance)

but it still resulted in

I found https://stackoverflow.com/questions/51956124/can-a-slack-bot-get-the-thread-id-that-a-slash-command-was-sent-from previously, and looked through some of the related links but am not sure there's been an update (i.e. whether it should work at all, separately from whether it's configured correctly)

If you can getting a working configuration in another Slack app, I'd be happy to apply the changes required, but otherwise I think that's the missing piece - feel free to use the hosted copy above for testing though 😐

[arkie]

Closing this out given https://api.slack.com/interactivity/slash-commands 😞

Limitations on use Slash Commands cannot be used in message threads. Consider using app shortcuts for this purpose instead.