bdashore3/CourtJester

Update system

Closed this issue · 1 comments

Perhaps it's not the best to update on every commit.

Migrate to either:

  • Using travis-ci for building
  • Restart the bot on command

Updating on every commit is fine now that I have separated GH actions workflows into multiple events.

Releases will be auto-built when published and from there, people can download the raw binaries.

The info command solves the issue of not seeing when the bot has restarted.