ducas.blogg.se - Github slack integration

Show details of pull request (number of commits, number of changed files, labels, milestone). Thread comments posted at the same time, such as comments to pull request code. Show actor of comment events on pull request. Show actor of pull request review events. Set whether to show the actor (user who took action) icon and name. At the same time, it should not include every sneeze in your GitHub account and be ignored by your teammates (agree on rules to check it 1–2 times per day at a certain time).Types: issues: If the necessity is just to get notifications about standard processes like pull requests, commits, branches, issues, releases and so on and so forth, better and simpler to enable this integration in 5 minutes.įrom my point of view, integration should be enabled by default for any project.

After that, you should link your account/organization with it by using commands like sign in, subscribe, unsubscribe. Just open the link, give permission to the application and use the /invite command to add GitHub integration to the channels you need. The easiest way is to use Slack integration. So, let’s have a look at the options that Slack and GitHub could offer us and see how to use them in basic scenarios.

GitHub Actions is applied as a tool for CI/CD.

Our application is multi-region and has a separate deployment workflow for each region.

Since our project and teams use Slack as a primary notification and messaging app, and GitHub Actions as a CI tool, we came up with the idea of integrating Slack notifications into our CI workflow. Of course, we received an email, but who on earth reads them? And obviously, when something goes wrong, we want to know right away because it could have a huge impact on our end users. That’s not really appropriate when one knows about a failure only after some time has passed. A few months ago, while enjoying peace and quiet, we got a message from our support department that one of our deployments suddenly failed.