2020-10-24 23:57:45 +05:30
---
2023-06-20 00:43:36 +05:30
stage: Deploy
group: Environments
2022-11-25 23:54:43 +05:30
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
2020-10-24 23:57:45 +05:30
---
2021-02-22 17:27:13 +05:30
# ChatOps on GitLab.com
2019-09-04 21:01:54 +05:30
2019-09-30 21:07:59 +05:30
ChatOps on GitLab.com allows GitLab team members to run various automation tasks on GitLab.com using Slack.
2019-09-04 21:01:54 +05:30
## Requesting access
2021-02-22 17:27:13 +05:30
GitLab team-members may need access to ChatOps on GitLab.com for administration
2019-09-30 21:07:59 +05:30
tasks such as:
2019-09-04 21:01:54 +05:30
2019-09-30 21:07:59 +05:30
- Configuring feature flags.
2019-09-04 21:01:54 +05:30
- Running `EXPLAIN` queries against the GitLab.com production replica.
2019-12-04 20:38:33 +05:30
- Get deployment status of all of our environments or for a specific commit: `/chatops run auto_deploy status [commit_sha]`
2019-09-04 21:01:54 +05:30
2021-02-22 17:27:13 +05:30
To request access to ChatOps on GitLab.com:
2019-09-04 21:01:54 +05:30
2021-02-22 17:27:13 +05:30
1. Sign in to [Internal GitLab for Operations ](https://ops.gitlab.net/users/sign_in )
2022-07-16 23:28:13 +05:30
with one of the following methods (Okta is not supported):
2021-02-22 17:27:13 +05:30
2023-03-17 16:20:25 +05:30
- The same username you use on GitLab.com.
2023-01-13 00:05:48 +05:30
- Selecting the **Sign in with Google** button to sign in with your GitLab.com email address.
2021-02-22 17:27:13 +05:30
1. Confirm that your username in [Internal GitLab for Operations ](https://ops.gitlab.net/ )
is the same as your username in [GitLab.com ](https://gitlab.com/ ). If the usernames
2023-03-17 16:20:25 +05:30
don't match, update the username in [User Settings/Account for the Ops instance ](https://ops.gitlab.net/-/profile/account ). Matching usernames are required to reduce the administrative effort of running multiple platforms. Matching usernames also help with tasks like managing access requests and offboarding.
2021-02-22 17:27:13 +05:30
1. Comment in your onboarding issue, and tag your onboarding buddy and your manager.
Request they add you to the `ops` ChatOps project by running this command
2023-01-13 00:05:48 +05:30
in the `#chat-ops-test` Slack channel, replacing `<username>` with your GitLab.com username:
2021-02-22 17:27:13 +05:30
`/chatops run member add <username> gitlab-com/chatops --ops`
2021-03-11 19:13:27 +05:30
```plaintext
Hi < __BUDDY_HANDLE__ > and < __MANAGER_HANDLE__ > , could you please add me to
the ChatOps project in Ops by running this command:
`/chatops run member add <username> gitlab-com/chatops --ops` in the
`#chat-ops-test` Slack channel? Thanks in advance.
```
2021-02-22 17:27:13 +05:30
1. Ensure you've set up two-factor authentication.
1. After you're added to the ChatOps project, run this command to check your user
status and ensure you can execute commands in the `#chat-ops-test` Slack channel:
```plaintext
/chatops run user find < username >
```
The bot guides you through the process of allowing your user to execute
commands in the `#chat-ops-test` Slack channel.
1. If you had to change your username for GitLab.com on the first step, make sure
[to reflect this information ](https://gitlab.com/gitlab-com/www-gitlab-com#adding-yourself-to-the-team-page )
on [the team page ](https://about.gitlab.com/company/team/ ).
2019-09-04 21:01:54 +05:30
## See also
2021-03-11 19:13:27 +05:30
- [ChatOps Usage ](../ci/chatops/index.md )
2022-08-27 11:52:29 +05:30
- [Understanding EXPLAIN plans ](database/understanding_explain_plans.md )
2021-04-17 20:07:23 +05:30
- [Feature Groups ](feature_flags/index.md#feature-groups )
