WIP: Bleatbot

[NotNite]

From #37, I present to you: Bleatbot!

Our very own beepy-boopy GitHub bot. See the (very lazily written) DIP for info.

I expect to revise the DIP in a bit, feel free to comment if I was too lazy at points. Also I stole a bunch of text from DIP29.

[philpax]

Sorry, should've gotten back to you earlier. This seems pretty reasonable to me - might be nice to get opinions from other members of @goatcorp/community-moderation to see if they have any needs they think should be addressed.

[NotNite]

I ask of someone to invite the bot to the GitHub organization so I can check who can use it based on if they're in the organization.

[philpax]

I've taken the liberty of inviting bleatbot. pls don't aboos api access

This also looks good for inspiration on automating the DIPs if we want to: https://github.com/rust-lang/rfcbot-rs. Here's a good example of it in use: rust-lang/rust#94119

[NotNite]

Maybe I'll clean up my profanity in the Git history and we can make a goatcorp/bleatbot repo so other people can help contribute. I'm a bit bad at writing good code... lol

[NotNite]

I ask of someone to invite the bot to the GitHub organization so I can check who can use it based on if they're in the organization.

Implemented this. My Git history is a bit messy so I'm definitely going to wipe it when I publish it, but it should be not-awful-enough to go on goatcorp/bleatbot if we're okay with making it.

[philpax]

@bleatbot exists but doesn't implement this DIP, afaik. Do we close this?

[NotNite]

No. It implements this DIP. I am waiting on goat's approval to move to its own repository under goatcorp/.

[philpax]

What's doing the bleatbot, approve stuff then?

[NotNite]

I believe a serverless function? It should ideally be moved to bleatbot's TS codebase in the future.

[philpax]

@goaaats can you provide some clarity around what @bleatbot is doing/running and where the code for that lives? Once that's clarified we'll unify that with the bleatbot codebase, update this DIP, merge it in, and bring bleatbot into the corp

[goaaats]

The only thing I run atm re: bleatbot is a CF worker that dispatches builds for plogon, here's the code(has CD set up): https://github.com/goatcorp/worker-plugindispatch/actions

[philpax]

@NotNite do you think it'd be possible to integrate that dispatcher into your code? Does it need to be integrated?

[NotNite]

I'm not sure if it needs to be integrated, but it would probably be easy to pull off. I think the real concern is finding people to help develop Bleatbot as I'm starting school soon.

[philpax]

That's fine, we can just get it up and running and build up new features as required. If we start on #46, deploying bleatbot to somewhere on goatcorp infra should be pretty easy. Given there's no general objection to the concept or implementation, I'm going to merge this and we can work out the specifics of implementation as we go.

[Bluefissure]

The only thing I run atm re: bleatbot is a CF worker that dispatches builds for plogon, here's the code(has CD set up): https://github.com/goatcorp/worker-plugindispatch/actions

Hi @goaaats and @NotNite, I worked on some of the rebuild functions into bleatbot to trigger the workflow. ottercorp/bleatbot@66469e9

Since I don't have access to the worker-plugindispatch repo I can only guess the behaviour of the command. No cooldown is introduced for now.

If it looks okay I can make a PR to bleatbot, but I think it's better to compare it with worker-plugindispatch first.