You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be good if the bot retrieved its version directly from the Github releases. Surely there's some git file we can use to get this information. If there is, then we can safely remove the version variable from the data file.
The text was updated successfully, but these errors were encountered:
It's not garunteed the bot is running the latest release. For us, it should be, but its not garunteed. You'd have to cross reference the file and all releases on github which doesn't sound like its built into github.
It doesn’t matter if it’s the latest release or not (although we only do a release when we want Sirius III to run the code, so it should be the latest anyway). What I mean is that when you pull from GitHub you also pull a gitconfig file among other files. If these were included in a release (likely not since the release is just the clean working environment, whereas the pull is the messy git-ridden one) then we should be able to get the version number automatically. I’m not talking about doing a manual comparison of every file to see which commit matches the current directory
It would be good if the bot retrieved its version directly from the Github releases. Surely there's some git file we can use to get this information. If there is, then we can safely remove the version variable from the data file.
The text was updated successfully, but these errors were encountered: