Manage and track your GitLab merge requests right in Slack with Actioner. Start using the app in Slack immediately after you install it.
Actioner provides a seamless GitLab MR Slack integration. Ship code faster by improving your MR review process and boosting engagement. Improve software release cycles by saying goodbye to stale MRs. End context-switching through managing your GitLab MRs in Slack. Keep your team and branches up-to-date with contextual notifications and dedicated Slack channels.
## Features
- **Ephemeral Slack channels for MRs:** These channels are used for MR assignees and reviews to get updates and collaborate on merge requests.
- **Check suit results:** Actioner collects completed check suits in a single thread and allows your teams to track them from the MR channel.
- **Conversation sync:** GitLab comments are directly sent to the ephemeral MR channel as Slack messages organizing cluttered conversations.
- **Broadcast channels for commits:** Your team gets notified of new commits to the main branch ensuring their branches stay up-to-date.
## How it works
Once you install this app, you just need to connect to your GitLab account and Slack workspace.
Each time there is a new merge request in GitLab, Actioner creates a dedicated Slack channel. It gathers assignees and reviews in that channel, sends MR details, and sends check-suit results. GitLab comments are also sent to the channel, allowing for streamlined communication.
Your team collaborates seamlessly in Slack and delivers faster & better code reviews. And once an MR is merged, Actioner archives the MR channel to reduce clutter in Slack.
Once an MR is merged, your team gets a message about new commits to the main branch in the Broadcast channel, attached with a link to view differences. With Actioner’s GitLab Merge request management, your team’s branches always stay up-to-date.
Workflows
Send message when MR is approved
This workflow automatically sends a message to the dedicated Slack channel when it is approved.
Comment on a merge request
Run this workflow to add a note (comment) on a GitLab merge request.
Approve merge request
Run this workflow to approve a merge request.
Send message when pipeline hook is received
This workflow automatically sends a message to the MR's dedicated channel when a pipeline hook is received. The hook status will be posted under a thread message.
Send message when MR is reopened
This workflow automatically sends a direct message to the MR owner if a merge request is reopened.
Create merge request channel
This workflow automatically creates a dedicated Slack channel when a merge request is opened.
Send message when MR is merged
This workflow automatically sends a message to the merge request Slack channel when it is merged
Notify MR assignee and reviewers
This workflow automatically sends a Slack message to the users when they are added as a reviewer to a merge request.
Add comment to merge request with pin emoji
This workflow is triggered when the pin emoji is put on a message in a dedicated merge request channel. The message content is automatically added to the merge request as a comment.
Merge a merge request
Run this workflow to merge a GitLab merge request.
Archive MR channel
This workflow archives the given Slack channel.
Onboard users who joined MR channel
When a user joins to MR updates channel, this workflow sends a direct message to the user from Slack. The message describes how to connect GitLab with Actioner and how to use the merge request review app.
Subscribe to GitLab events
This workflow creates a webhook on GitLab to subscribe to the merge request events from a selected project. If you want to subscribe events from multiple projects, you can re-run this workflow.
Notify channel when a commit is pushed to default branch
This workflow sends a message to the preselected main/master branch updates Slack channel when a new commit is pushed
Archive channel when MR is closed
When MR is closed or merged, this workflow sends a message that the channel will be archived and archives the Slack channel of the MR.
Send message when MR comment is added
This workflow automatically sends a message to the MR's dedicated Slack channel when someone posts a comment.
Delete branch
This workflow deletes GitLab branch
Set merge request update channel
This workflow creates a merge request channel on Slack with a given prefix. (#-gitlab-updates) Anyone who joins this channel will receive an onboarding message from Actioner to explain how to connect GitLab. Also, when a commit is pushed to the main branch, a message will be sent to this channel to notify your team.
Security & Compliance
Privacy & data governance
Data retention policy
For the most up to date policy information, always refer to: https://actioner.com/privacy-policy , https://actioner.com/gdpr and https://actioner.com/security. How long we keep your data prior to the deletion of data or termination of the contract between the customer and Actioner depends on the type of data, as described in further detail below:
Account data: Personal data that relates to customers’ relationship with the Actioner, including your workspace details, user accounts and your billing information. We retain your account information for as long as your account is active. We also retain some of your information as necessary to comply with our legal obligations, to resolve disputes, to enforce our agreements, to support business operations, and to continue to develop and improve our Services. Where we retain information for Service improvement and development, we take steps to eliminate information that directly identifies you, and we only use the information to uncover collective insights about the use of our Services, not to specifically analyze personal characteristics about you.
Configuration data: Any configuration or personal data that is required by Actioner to be functional for the customer, such as (a) applications and their sub-configurations like workflows, documents or functions, (b) credentials, connections and integrations with the third party providers, (c) identity and access management related personal data. Actioner stores and processes configuration data for the permitted purposes until the customer elects to delete such configuration data via the service and the customer is solely responsible for deleting configuration data.
Usage data: (a) Inputs, requests and form data provided by the end users or clients of the customer, (b) any data that is programmatically, periodically or automatically received through an integration of the customer, (c) any content stored as a result of processing a configuration data, (d) activity logs used to identify the source of service requests. Actioner deletes any stored usage Data sixty (60) days after the data is produced.
Data archiving and removal policy
For the most up to date policy information, always refer to: https://actioner.com/privacy-policy , https://actioner.com/gdpr and https://actioner.com/security. Whenever a user account is deleted by a workspace admin, Actioner automatically deletes all data stored within the context of the deleted user account like profile information and the credentials / connections for the third party integrations. Whenever an app is deleted by an app admin, Actioner automatically deletes all data stored within the context of the app like tables, records, workflow, docs, files, etc. Whenever the workspace deletion is initiated by a workspace admin, Actioner automatically deletes all data stored within the context of workspace after a waiting period of 72 hours. After the waiting period, the deletion may take up to 10 days after the termination effective date. When any data is deleted, the archived copy of the data on Actioner’s backup systems will remain for 30 days and the backup data will be securely isolated and protected from any further processing, except as otherwise required by applicable law or regulation.
Data storage policy
At Actioner, ensuring the security of our users' data is paramount. To this end, we employ robust cryptography policies and practices. All data stored within our systems is encrypted at rest using the AES256 encryption standard, providing an additional layer of protection against unauthorized access. Furthermore, we uphold strict encryption standards for data in transit, both within our internal networks and over public channels. All data transmissions utilize TLS1.2 or higher encryption protocols, safeguarding information from interception or tampering. In terms of cryptographic key management, we rely on the AWS Key Management Service (KMS) for secure and controlled handling of cryptographic keys. This includes secure key generation, restricted access, secure storage, regular backups, and periodic rotation of keys. Our integration with AWS services streamlines the encryption process and enhances control over access to keys, thereby bolstering the overall security of our platform.We operate a comprehensive backup program at Actioner. This includes our internal systems, where our backup measures are designed in line with system recovery requirements. With respect to our cloud services, and specifically referring to you and your application data, we also have extensive backup measures in place. Our data backups are retained for 30 days with support for point-in-time recovery and are encrypted using AES-256 encryption.
Data center location(s)
United States
Data hosting details
Actioner is a cloud-native product whose infrastructure is hosted on industry-leading cloud provider Amazon Web Services (AWS). Actioner cloud services and data are hosted on Amazon Web Services (AWS). Where all our computing, messaging, network, and storage layers are located in the US West, our browser application is distributed via our CDN network all over the world. As a design standard, all Actioner services as well as the upstream computing, messaging, network and storage services are running on multiple availability zones (AZs) so that the traffic and the data are distributed among them. This design allows us to tolerate zone-specific failures with no downtime. This multi-zone high availability is the first line of defense for geographic and environmental risks and means that services running in multi-AZ deployments should be able to withstand AZ failure.
Data hosting company
Amazon Web Services (AWS)
App/service has sub-processors
Yes
Guidelines for sub-processors
Certifications & compliance
SOC attestation
Privacy policy
GDPR commitment
Data deletion request procedure
Security
Supports Single Sign On (SSO) with the following providers
Google, Slack, Okta
Supports Security Assertion Markup Language (SAML)
No
Has a dedicated security team
Yes
Contact for security issues
Has a vulnerability disclosure program
Yes
Vulnerability disclosure program URL
Vulnerability disclosure program covers Slack app
Yes
Has a bug bounty program
Yes
Bug bounty program URL
Requires third party authorization/connections
No
Third party services used by this app
Uses token rotation
No
Contributors
Actioner
.png){kind=spacer}
