debian-mirror-gitlab/doc/user/project/integrations/gitlab_slack_application.md

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

81 lines
3 KiB
Markdown
Raw Normal View History

2020-10-24 23:57:45 +05:30
---
2021-10-27 15:23:28 +05:30
stage: Ecosystem
group: Integrations
2021-02-22 17:27:13 +05:30
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
2020-10-24 23:57:45 +05:30
---
2021-03-11 19:13:27 +05:30
# GitLab Slack application **(FREE SAAS)**
2019-07-31 22:56:46 +05:30
2021-02-22 17:27:13 +05:30
NOTE:
2019-07-31 22:56:46 +05:30
The GitLab Slack application is only configurable for GitLab.com. It will **not**
work for on-premises installations where you can configure the
2020-04-08 14:13:33 +05:30
[Slack slash commands](slack_slash_commands.md) service instead. We're planning
to make this configurable for all GitLab installations, but there's
2020-06-23 00:09:42 +05:30
no ETA - see [#28164](https://gitlab.com/gitlab-org/gitlab/-/issues/28164).
2019-07-31 22:56:46 +05:30
Slack provides a native application which you can enable via your project's
integrations on GitLab.com.
## Slack App Directory
The simplest way to enable the GitLab Slack application for your workspace is to
install the [GitLab application](https://slack-platform.slack.com/apps/A676ADMV5-gitlab) from
the [Slack App Directory](https://slack.com/apps).
2021-09-04 01:27:46 +05:30
Clicking install takes you to the [GitLab Slack application landing page](https://gitlab.com/-/profile/slack/edit)
2019-07-31 22:56:46 +05:30
where you can select a project to enable the GitLab Slack application for.
## Configuration
Alternatively, you can configure the Slack application with a project's
integration settings.
2022-05-07 20:08:51 +05:30
Keep in mind that you must have the appropriate permissions for your Slack
team to be able to install a new application, read more in Slack's
documentation on [Adding an app to your workspace](https://slack.com/help/articles/202035138-Add-apps-to-your-Slack-workspace).
2019-07-31 22:56:46 +05:30
2021-02-22 17:27:13 +05:30
To enable the GitLab service for your Slack team:
2019-07-31 22:56:46 +05:30
2020-10-24 23:57:45 +05:30
1. Go to your project's **Settings > Integration > Slack application** (only
2020-05-24 23:13:21 +05:30
visible on GitLab.com).
2022-05-07 20:08:51 +05:30
1. Select **Add to Slack**.
2019-07-31 22:56:46 +05:30
That's all! You can now start using the Slack slash commands.
2020-05-24 23:13:21 +05:30
## Create a project alias for Slack
To create a project alias on GitLab.com for Slack integration:
1. Go to your project's home page.
2022-05-07 20:08:51 +05:30
1. Go to **Settings > Integrations** (only visible on GitLab.com)
1. On the **Integrations** page, select **Slack application**.
2020-05-24 23:13:21 +05:30
1. The current **Project Alias**, if any, is displayed. To edit this value,
2022-05-07 20:08:51 +05:30
select **Edit**.
1. Enter your desired alias, and select **Save changes**.
2020-05-24 23:13:21 +05:30
Some Slack commands require a project alias, and fail with the following error
if the project alias is incorrect or missing from the command:
```plaintext
GitLab error: project or alias not found
```
2019-07-31 22:56:46 +05:30
## Usage
After confirming the installation, you, and everyone else in your Slack team,
2020-04-22 19:07:51 +05:30
can use all the [slash commands](../../../integration/slash_commands.md).
2019-07-31 22:56:46 +05:30
2021-02-22 17:27:13 +05:30
When you perform your first slash command, you are asked to authorize your
2019-07-31 22:56:46 +05:30
Slack user on GitLab.com.
2020-04-22 19:07:51 +05:30
The only difference with the [manually configurable Slack slash commands](slack_slash_commands.md)
2019-07-31 22:56:46 +05:30
is that all the commands should be prefixed with the `/gitlab` keyword.
We are working on making this configurable in the future.
2019-12-21 20:55:43 +05:30
For example, to show the issue number `1001` under the `gitlab-org/gitlab`
2019-07-31 22:56:46 +05:30
project, you would do:
2020-04-08 14:13:33 +05:30
```plaintext
2019-12-21 20:55:43 +05:30
/gitlab gitlab-org/gitlab issue show 1001
2019-07-31 22:56:46 +05:30
```