Infer type implicitly

[whilefoo]

Resolves ubiquity-os/ubiquity-os-kernel#45

Why do we have config duplicated here and in the kernel repo? I'm not even sure why the kernel configuration needs to be in a separate package because it won't be used by plugins?

There appears to be a env schema in this repo that looks like its from the old bot, @gentlementlegen do you know if it's even used anywhere?

[github-actions]

Lines	Statements	Branches	Functions
	Unknown% (0/0)	Unknown% (0/0)	Unknown% (0/0)

JUnit

Tests	Skipped	Failures	Errors	Time
0	0 💤	0 ❌	0 🔥	4.46s ⏱️

[gentlementlegen]

@whilefoo used to be this way since configuration was shared in a few repositories and was not sent as we do now through the kernel, leading to a lot of duplicated code, which this package solved. I guess now it would become obsolete with the new architecture.

But I am a bit confused about why you are making these changes to the old bot? The new kernel already has the capability to read urls or Actions, when I made the issue you mentioned I thought simply about removing the type and updating the related configuration (can't add multiple reviewers to that one somehow).

[0x4007]

Suggested change

	function githubPluginType() {
	function githubPluginType(): Plugin {

It might be safer to declare the type here instead of typecasting it below

[whilefoo]

But I am a bit confused about why you are making these changes to the old bot?

I thought this repo is still used, we should archive it then

[gentlementlegen]

@whilefoo Repo is still used for the production but is in maintenance mode right now I guess, if you can confirm @0x4007

[0x4007]

@whilefoo Repo is still used for the production but is in maintenance mode right now I guess, if you can confirm @0x4007

The work in this repo should not be prioritized, in favor of shipping v2 of the bot. However, for some critical fixes, yes we can push and deploy here.

[0x4007]

@whilefoo @gentlementlegen I just realized this is for the npm module, which indeed is being used in the new bot lol sorry about that.

This repo is not github.com/ubiquity/ubiquibot

I might rebrand the project to https://github.com/ubiquity-os and then have a project under there called kernel or something. Perhaps we can leave behind the ubiquibot terminology, and relegate it to refer to v1.