Bugfix

Prior to this, any job which needed the values {{ .Time }} and {{ .Date }} would frequently get the wrong values.

This is because we computed this values once, when the bot started up, and then never updated them. The data and time reflected the date and time the bot was started, and not the date and time when a scheduled task was to run

Bugfix

Prior to this, any job which needed the values {{ .Time }} and {{ .Date }} would frequently get the wrong values.

This is because we computed this values once, when the bot started up, and then never updated them. The data and time reflected the date and time the bot was started, and not the date and time when a scheduled task was to run

Remove stupid, half-cut, shit motd

Revert "Do a big ol' banner every morning"

This was a half-cut commit. What was I even thinking? It's shit.

It's a total hack, too- it doesn't even show up in the commands list-
I even had to hack around displaying commands because it was so ill
thought out.

Instead, I've created a noddy little bot that prints an MOTD. Same
effect, and without compromising this project with a hidden command.

This reverts commit 29a3bfcbecc99a2ad3137bc6cf1d0ef079c26f72.

Rehome

v1.2.0

Update name, bottom to new org

v1.1.1

Only show jobs

Draw some ascii art

This is totally needless and probably ruins the whole thing

Bugfix

Some events were not being loaded from disk :/

Bugfix

Ensure the correct timezone is used in template values.

Initial, stable version

Includes:

1. Clean and tidy table showing set schedules
2. An allow list to enable users to add new schedules
3. Ability to query/ add schedules in a private chat (There's still a global schedule table)