Open 0x4007 opened 7 months ago
/start
I'll carry on anyway
Skipping /start
because it is disabled on this repo
@pavlovcik would it be a good idea to have a /config help
or /config --help
and we'll have GPT explain the config structure or list what can be set?
Base off of a commit anytime after that one.
I'm guessing that /config would be more so for first time setup? Or was this in reference to basing the implementation on a commit after that one? lmao
I'm thinking that I'll just have gpt call generateConfiguration(context: ProbotContext)
which will provide an up to date config object and the bot can inject the admin specified entries only leaving missing props out.
Help should be in the help menu. Don't make a sub help menu.
The commit I'm referring to is when we refactored all of the configuration hierarchy on my fork.
generateConfiguration(context: ProbotContext)
Seems like a sensible start.
Probably should also
fs.readFileSync
to pass in the AJV information.This will need to use the new config schema we recently implemented at https://github.com/pavlovcik/ubiquibot/pull/45#issuecomment-1815335346
Base off of a commit anytime after that one.