build: include git-describe version as part of the bot in /ping command#1422
build: include git-describe version as part of the bot in /ping command#1422christolis wants to merge 1 commit intoTogether-Java:developfrom
Conversation
It is uncertain on which version the bot is running in production, and
those with a lack of access to the production infrastructure have almost
no way to get such information.
Expand the "/ping" slash command to actually mention which version it is
running as well as the date on which it was built, more specfifically it
now says:
> Pong! Running on version v1.2.3-g1a2b3c (2026-02-28)
That way we don't have to approach the lucky few folks with access and
badger them with primitive questions. :)
Signed-off-by: Chris Sdogkos <[email protected]>
Zabuzard
left a comment
Zabuzard
left a comment
There was a problem hiding this comment.
the /ping command acts as minimal and simplest introduction for learners.
i would appreciate not cluttering up its code and its unit-test for this feature.
we can add a /version command instead. i like the idea in general but have some doubts whether this will work properly in all environments, on the VPS, with docker and whatnot. so would be great if @marko-radosavljevic or @tj-wazei will review this
|
It's also not something contributor should worry about. Prod is always latest commit on master, unless something is seriously broken. And if something is seriously broken, only people with access to the vps are the ones that can fix it anyway. Dev server is always latest commit on dev, CI/CD is automatic, so everything happens on push. You can see successful deployment by passing gh actions on merge. Nobody pushes or does to these branches otherwise, they are protected. I don't want to add unnecessary confusion and noise to beginners, and we never had issues with version confusion in 5 years of the project lifecycle. We can have a /version command, I guess. Should be easy to implement, and I will give my review to make sure it works reliably in our environment. |
3 participants
It is uncertain on which version the bot is running in production, and those with a lack of access to the production infrastructure have almost no way to get such information.
Expand the "/ping" slash command to actually mention which version it is running as well as the date on which it was built, more specfifically it now says:
That way we don't have to approach the lucky few folks with access and badger them with primitive questions. :)