- Introduced in GitLab 9.4.
- Distributed to Slack App Directory in GitLab 10.2.
Slack provides a native application which you can enable via your project’s integrations on GitLab.com.
Clicking install will take you to the GitLab Slack application landing page where you can select a project to enable the GitLab Slack application for.
Alternatively, you can configure the Slack application with a project’s integration settings.
Keep in mind that you need to have the appropriate permissions for your Slack team in order to be able to install a new application, read more in Slack’s docs on Adding an app to your workspace.
To enable GitLab’s service for your Slack team:
- Go to your project’s Settings > Integration > Slack application (only visible on GitLab.com).
- Click Add to Slack.
That’s all! You can now start using the Slack slash commands.
To create a project alias on GitLab.com for Slack integration:
- Go to your project’s home page.
- Navigate to Settings > Integrations (only visible on GitLab.com)
- On the Integrations page, click Slack application.
- The current Project Alias, if any, is displayed. To edit this value, click Edit.
- Enter your desired alias, and click Save changes.
Some Slack commands require a project alias, and fail with the following error if the project alias is incorrect or missing from the command:
GitLab error: project or alias not found
After confirming the installation, you, and everyone else in your Slack team, can use all the slash commands.
When you perform your first slash command you will be asked to authorize your Slack user on GitLab.com.
The only difference with the manually configurable Slack slash commands
is that all the commands should be prefixed with the
We are working on making this configurable in the future.
For example, to show the issue number
1001 under the
project, you would do:
/gitlab gitlab-org/gitlab issue show 1001