Manage and track your GitHub pull requests right in Slack with Actioner. Start using the app in Slack immediately after you install it.
Actioner provides a seamless GitHub PR Slack integration. Merge pull requests faster by improving your PR review process and increasing engagement. Say goodbye to stale PRs and improve software release cycles. End context-switching by managing your GitHub PRs in Slack
## Features
- **Ephemeral Slack channels for PRs:** PR stakeholders get updates, communicate and collaborate on code changes in this channel.
- ** Take action on PRs**: Merge and close pull requests right in Slack.
- **Check suit results:** Actioner collects completed check suits in a single thread and allows your teams to track them from the PR channel.
- **Conversation sync:** GitHub comments are directly sent to the ephemeral PR channel as Slack messages, organizing cluttered conversations.
- **Broadcast channels for commits:** Your team gets notified of new commits to the main branch in a dedicated Slack channel to keep their branches up-to-date.
## How it works
Actioner creates a dedicated Slack channel named after the PR whenever there is a new pull request in GitHub. It brings assignees and reviews to that channel, sends PR details, and collects check-suit results. GitHub comments also appear in the PR channel to get conversations synced.
Actioner lets your team collaborate seamlessly and deliver faster & better code reviews. And once a PR is merged, the channel gets archived to reduce clutter in Slack.
In the Broadcast channel, your team gets informed about the new commits to the main branch after a PR is merged. Actioner sends a message by attaching a link to view differences so that their branches can stay up-to-date.
Keep your team and branches up-to-date with contextual notifications and dedicated Slack channels.
Workflows
Set PR update channel
This workflow creates a channel on Slack with a given prefix. (#-github-main-pushes) Anyone who joins this channel will receive an onboarding message from Actioner to explain how to connect GitHub. Also, when a commit is pushed to the main branch, a message will be sent to this channel to notify your team.
Send button to ask AI for review
Sen a button to ask AI assistant for a review when a pull request is created
New assistant message received
Archive PR channel
This workflow archives the given Slack channel.
Add user messages to Assistant context
Ask AI Assistant for a review
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
Add new commit to branch
Send Slack message when pull request commented
Sends a message to the channel whenever a new comment is added to a pull request.
Setup pull request channel
This step creates a Slack channel when there is a new pull request. It also sets the channel's purpose, invites the PR assignees and reviewers to the channel, and adds the URL to the PR as a comment.
Select GitHub action app
Run this workflow to select the GitHub actions app that will be mapped with this app. Once GitHub actions app is mapped, its actions will be available in dedicated PR channels.
Approve a merge request
Use this workflow to approve a merge request.
Send message when PR is merged
Sends a message to related PR channel when an PR is merged.
PR reminder
This workflow finds long running PRs and reminds PR owners via Slack.
Onboard users who joined master push channel
When a user joins to GitHub Push updates channel, this workflow sends a direct message to the user from Slack. The message describes how to connect GitHub with Actioner and how to use the pull request review app.
List pull requests
This workflow returns the list of PRs for a selected repository.
Send Slack message when review submitted to PR
Sends a message to a pull request channel whenever a pull request related is approved.
Subscribe to GitHub events
This workflow creates a webhook on GitHub to subscribe to the pull request events from a selected repository. If you want to subscribe PR events from multiple repositories, you can re-run this action. Note that you must have the permission to create a webhook in your selected repository to be able to subscribe to GitHub events.
Add comment to pull request with pin emoji
This workflow creates a pull request comment whenever the pin emoji is added to a message in a dedicated pull request channel.
Merge pull request
Run this workflow to merge pull requests into a base branch.
Assistant run status
Send message when check suite is completed
Sends a thread message whenever a check suite is completed.
Talk to AI Assistant via Slack message
Get file contents
Gets the contents of a file in a Github repository.
Send message when PR is reopened
This workflow automatically sends a direct message to the PR owner if a pull request is reopened.
Archieve channel when PR is closed
This workflow automatically archives a PR channel when PR is closed.
PR events publisher
This workflow publishes PR events.
Invite PR reviewer to channel
This workflow automatically invites reviewers to the PR channel and sends an informative message.
Delete branch
This workflow deletes the given GitHub branch.
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}
