| Commit message (Collapse) | Author | Lines |
|
It is not necessary for these to be coroutines.
Co-authored-by: MarkKoz <[email protected]>
|
|
This should be more readable.
Co-authored-by: MarkKoz <[email protected]>
|
|
Reduces code duplication.
Co-authored-by: MarkKoz <[email protected]>
|
|
Co-authored-by: MarkKoz <[email protected]>
|
|
* Capitalize month names
* Add backticks to `sha` attr reference
* Avoid misusing the term 'poll'
Co-authored-by: MarkKoz <[email protected]>
|
|
Co-authored-by: MarkKoz <[email protected]>
|
|
Co-authored-by: MarkKoz <[email protected]>
|
|
Previously, the env var was only being used for seasonal decorators,
not branding. Although for testing purposes, seasons can be easily
set via bot commands, it makes sense to also use the env var to
choose the current season.
|
|
The function is useful to other modules as well - not only decorators.
This declares it as public and moves it to a more accessible place.
|
|
Constant is no longer used.
See: 9259f985e6e327a522b4420c879a50cb4f75a09d
|
|
A persistent config file will remember whether the daemon is supposed
to be running, or not. This means that instead of relying on the env
variable, the daemon can be turned on or off "once and for all"
via a command, and will not violate this decision on restart.
This effectively deprecates the `Branding.autostart` env var. It is
believed that having two ways to configure the same thing would
be more confusing than useful. The env var will be removed.
The two helper functions for reading and writing have been implemented
in a generic manner, meaning that should a new config key be added in
the future, the helpers shouldn't require any further adjustments.
Suggested by lemon and scragly.
Co-authored-by: Leon Sandøy <[email protected]>
Co-authored-by: scragly <[email protected]>
|