 If you want to receive notifications on every commit in your GitHub repository, you can use wire and you can connect it with wire's GitHub action. Using wire's GitHub action you can get a ping on activity in your GitHub repository and this way you will be always up to date. But first we need to set it up. So simply click on the actions tab in your GitHub repo and there you will have a guide that helps you creating a workflow. Every workflow starts with a simple file. In this demo we will name it CI to match the name of our workflow and I will also guide you through the concept of workflows. Every workflow has jobs and those jobs can have steps. So we have the concept of workflow, jobs and steps. Let's commit it to have a basic setup and then we will check how this reflects on GitHub. First of all we have the .github and then the workflows directory and if we commit new configurations in there then those workflows will be automatically triggered. Here we have the first execution and we can see that there is the build job and this build job has then several steps that just got executed. Let's customize our workflow to meet our requirements. We can do it by just simply clicking on the pencil icon and in here we can now edit the workflow and I suggest that we remove all the comments so the one here on top can go and I will also remove the other two lines of comments here and of course the one above the job. By the way the job named build can be renamed so I will name it reporting to match our intention and then I will also just remove the last comments here and the first thing that we see now here in the step is that it uses the checkout action but here is the wire messenger and we can use this action instead of the checkout action. We actually don't need to check out the repository because all we want to do is sending a report and for this the wire messenger action is just about right and here we can now add some parameters. We can give some parameters with the whisk keyword and let's have a look back at the github action here from wire. We see that it requires some parameters like the email so I will just copy it over. I also like this hint here from github it's really helpful and we see that here I used the in secrets keyword and these are coming from the settings. So in the settings of your github repository you can set up some environment parameters like wire email or wire password and those can be used then in your github action. I've done that already in preparation so we can now go back here and use them directly for the email key. Next one is the password key for the password key we will also use a value from the secrets so here we use wire underscore password. Of course we need to decide which text we want to send and I will go with a very classic one and I put it in quotes to not mess up anything with spaces or special characters so we will just send hello world then for the sake of consistency an npline of code here and a commit to the main branch. We now have set up an email and a password we also do have a text but there's one thing that is missing which is the conversation id. Here we see that we can also pass it through an environment variable but we can also write it in plain text. How to get this conversation id it's actually quite easy if we click on any conversation wire we will see in the address bar a uu id and this one we can use I will just copy it over and then we are fine so let's go back to our workflow and pass another parameter here conversation and I will paste the id again in quotes just to be safe another commit on the main branch and then we are good to go so let's have a look at our workflows here we see all the commits that we have done so far and I screwed up the second commit because I wasn't passing any conversation id but the third one should be okay so if we go here in the reporting job then we can see that it sets up the job and it runs our github action the wire messenger action if we open it we can see the details and we see that a bot is running there on the production environment and it also sends the message hello world let's have a look if we go back to wire we can see that the demo account actually sent the message hello world that's cool we haven't even touched our id everything done just from the web interface in github we can also improve our script so so far we've been just sending hello world to wire but if we go back to our workflow we can make use of some environment variables coming from github so github for example provides a very specific event which we can access through github.event and then we can use the head commit that's the event name here and we will use the message of the head commit if we do this then we will not just get hello world but we will get the original commit message that's why I will write something specific here like use commit message and if I commit this to the main branch I can see the update of the action again in the actions tab there we have our use commit message and if we click on this commit we can then see the progress of course it takes a bit but just a few seconds so setting up the job is already in progress now runs the wire messenger github action here we see that it sent a message let's verify it and boom use commit message coming directly from our github commit by the way if you don't like this auto-generated step name you can also go and change it so in the dot github workflows directory in our workflow file we can go to the specific step and then give it a name property and for the name we can put anything we like for example send message who wire