Hello, this is a really short video. We're actually I think useful application that uses our chat. Ups features in a few different ways and it uses surveillance as well, basically to are combined. What does this app? Do? It's a github, breeze watcher. Why is it interesting?

Because in the service team, we have a few issues even that are waiting for some new releases, for example for Google and there as well some other cases where it's quite useful to know when new release, even if it's an r4 beta release comes out, especially quickly changing field like a native for this reason, I've created this project that receives as arguments github, repos and checks. If there's a new release from the past 24 hours, if you look at the readme, you can write in a few ways.

You cannot directly from your CLI using curl or you can revert a scheduled job and it will report to specify channel that you set up or you can write it as a gate lab chat operator. This is the one I'm going to show you right now. I've served a long time for a repo that actually has a new release today, so what I have to do? I just give the command / gitlab K into the examples, github Ruiz for sure this is specific to get lab dot-com.

If you are running the chat, ops on your own stand on instance, then you can have a your dedicated slash comments and you don't need this extra part. The que native examples part here that let you see then run says that this way we actually give live, chat, ops, command and run the check three pubs job and pass on a few arguments to it like AWS as they go report to be checked for newly's. The kennedy serving repo is checked for immunities and Unitec p.m. to project.

These checks for new Ruiz in this current case I know that the last one has a new release. I just have to click enter and now Joe is created in the backend. So basically, here in the pipeline's I can see the job running.

And it will send me back the response in the slack response here. We have to wait for job to finish. Of course, it doesn't like take long time, but in the current case, okay, we have already received oh and actually in both aw SS decay and Unitec really has a new release just to let you know a few minutes ago. This was really just a few hits ago the AWS SDK. So this is one of the ways to use it. Then we have the scheduled job as well, which I already set up here.

I have the repos to be set in advance that I want to check on daily basis. In this current case, neither of them has a new release, but now that I know that a sybilla's SDK actually has a new release. I would just add that here and save it and run it.

These jobs use slack slack hook, functionality, which means that they are tied to a specific channel where the result will be posted. This Web goes back back hook is set as a bribe all on the on the project, but actually it might be a good idea to set it on the scheduled job as well, and that way we can set up several jobs.

It means basically runs the same code as the Chatham's did, plus one extra step, which is to gather that output and send it over to slack. It will arrive shortly in a different channel right now and in the slack bot Channel, and this will arrive to my personal channel. So here we come and there is Jason problem. So this is basically the.

How things would work if they do, but actually never in demos? And besides this, you can run on coral as well, just by much less interesting.